• 1 Post
  • 3.28K Comments
Joined 3 years ago
cake
Cake day: July 3rd, 2023

help-circle
  • ChatGPT 5.6: (Is fat32 a good option for a 64gb external drive) FAT32 is suitable for a 64 GB external drive only when maximum compatibility is the priority.

    The main limitation is that individual files cannot exceed 4 GB. That makes FAT32 unsuitable for large videos, disk images, backups, or many game files.

    Better choices:

    exFAT: Best general-purpose option for Windows, macOS, Linux, TVs, consoles, and other modern devices. Supports files larger than 4 GB.

    NTFS: Better for a Windows-focused drive, permissions, and reliability, but has weaker write support on some non-Windows devices.

    ext4: Best for Linux-only use, but Windows and macOS do not support it natively.

    FAT32: Use mainly for older hardware, firmware updates, boot media, or devices that specifically require FAT32.

    For a normal 64 GB external drive, I would format it as exFAT unless the device you plan to connect it to explicitly requires FAT32.

    Local hardware Gemma-4-12b: (Is fat32 a good option for a 64gb external drive) For a 64GB external drive, ExFAT is usually a better choice than FAT32.

    Here is why:

    The 4GB File Limit

    The biggest issue with FAT32 is that a single file cannot exceed 4GB. While a 64GB drive can easily hold many thousands of small documents and photos, modern media files (high-definition videos, disk images, or large installer files) often exceed that limit. If you try to copy a 5GB file onto a FAT32 formatted drive, the copy will fail even though the drive is mostly empty.

    The Solution: ExFAT

    ExFAT was designed specifically for flash memory (thumb drives, SD cards, external drives). It keeps the high compatibility that makes FAT32 popular — it still works on Windows, macOS, Linux, Android, and PlayStation — but removes the file size ceiling, allowing files of virtually any size.

    Summary Recommendation

    • Use ExFAT if you might store large video files, large installers, or want the most modern standard for a drive of this size.
    • Use FAT32 only if you require the highest possible compatibility with very old hardware (e.g. a DSLR camera from 15 years ago or a legacy Windows XP machine) and your files will always stay under 4GB.













  • So gluetun is for docker networks and lets you isolate traffic to/from other docker containers into a VPN, you run it and qbt inside docker containers with gluetun configured to your vpn, then qbt configured to route all its traffic through it.

    Edit: I didn’t have to port forward at all on my network for this to access it locally (I run it on a separate computer), because all the “outside” traffic in qbt is going through the vpn that has a forwarded port seeders/leachers can connect (which is dynamically updated as it changes with the aforementioned qbt port manager)

    For example (truncated docker compose just the part related to above): services: qbittorrent-vpn: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent-vpn depends_on: gluetun: condition: service_started restart: true restart: unless-stopped network_mode: “service:gluetun”

    Then gluetun: services: gluetun: image: qmcgaw/gluetun container_name: gluetun restart: unless-stopped networks: - default cap_add: - NET_ADMIN devices: - /dev/net/tun - 8888:8888/tcp # HTTP proxy volumes: - /appdata/gluetun:/gluetun - /appdata/gluetun/tmp:/tmp/gluetun environment: TZ: $TZ VPN_SERVICE_PROVIDER: $GLUETUN_VPN_SERVICE_PROVIDER VPN_TYPE: $GLUETUN_VPN_TYPE # wireguard / openvpn WIREGUARD_PRIVATE_KEY: $GLUETUN_WIREGUARD_PRIVATE_KEY WIREGUARD_ADDRESSES: $GLUETUN_WIREGUARD_ADDRESSES VPN_PORT_FORWARDING: on VPN_PORT_FORWARDING_PROVIDER: protonvpn # or your provider VPN_PORT_FORWARDING_STATUS_FILE: /tmp/gluetun/forwarded_port # OPENVPN_USER: $GLUETUN_OPENVPN_USERNAME # OPENVPN_PASSWORD: $GLUETUN_OPENVPN_PASSWORD healthcheck: test: [“CMD”, “/gluetun-entrypoint”, “healthcheck”] interval: 5s timeout: 5s retries: 1 start_period: 10s

    gluetun-qbittorrent-port-manager: image: jopiermeier/gluetun-qbittorrent-port-manager:latest network_mode: “service:gluetun” container_name: gluetun-port-manager depends_on: gluetun: condition: service_started restart: true qbittorrent-vpn: condition: service_started restart: true environment: - QBITTORRENT_USER= - QBITTORRENT_PASS= - QBITTORRENT_PORT=$QBITTORRENTVPN_PORT volumes: - /appdata/gluetun/tmp:/tmp/gluetun



  • Gluetun itself already knows the forwarded port via NAT-PMP, this program just gets it from gluetun and assigns it in qbt via the qbt api and if it returns a 200 response it considers it confirmed, here’s an example log:

    waiting for qBittorrent WebUI…

    qBittorrent WebUI is ready (authenticated).

    port file did not contain an integer: /tmp/gluetun/forwarded_port

    port file did not contain an integer: /tmp/gluetun/forwarded_port

    gluetun provided forwarded port: 36884

    syncing port 36884 to qBittorrent…

    successfully updated qBittorrent to port 36884 (confirmed)

    port file did not contain an integer: /tmp/gluetun/forwarded_port

    port file did not contain an integer: /tmp/gluetun/forwarded_port

    gluetun provided forwarded port: 39293

    syncing port 39293 to qBittorrent…

    successfully updated qBittorrent to port 39293 (confirmed)