• 0 Votes
    11 Posts
    4k Views
    mituM

    @pyr0cide Just leave the exports on the server

    /volume1/roms 192.168.1.*(rw,async,no_wdelay,no_root_squash)

    And make sure you use the proper case when referring to the share name, i.e. not mixing upper-case with lower-case

    mount -t nfs -o vers=3 192.168.1.6:/volume1/roms /home/pi/RetroPie/roms
  • 0 Votes
    3 Posts
    875 Views
    TeathiefT

    @zerojay I've been using compression for years now admittedly on arch though which means I may have
    had a newer version of btrfs then is in debian currently this whole time.

    Quite a few power outages during that time its been as a whole 100x more stable then my experience with XFS ever was and that gets recommended for extremely large data deployments (don't know why XFS eats data on any system I've used it on).

    My raspberry has the same disk size as my main desktop SSD, 128GB is a little cramped by modern standards but I don't think I'll be riding 90% the whole life of my Pi.

    Might be harder on microsd's but frankly isn't ext4 itself known to be extremely rough on microsd storage as well?
    Its complained about when it comes to android phones but they just don't expect the phone to be around long enough for it to be a problem.

    Fragmentation might be a valid argument but I've never noticed a issue with it, still seems as snappy as when I first put the filesystem on my system.

    Just did a fragmentation scan on my drive besides a couple files with 19 and 54 extents 99% of them are sitting at 1 extent.