Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My understanding is that FSFS is intended for solid state drives, which are a rather different animal. SSDs and SD cards are both flash media, but have different use cases and requirements.
My desktop boots from an SSD, and applications all live there. Data tends to live elsewhere. I have an assortment of USB thumbdrives that are used for backups and data I need to be portable. Those come formatted as FAT32 or exFAT, and I leave them that way. Linux can read and write FAT32 cards using the built-in support in the kernel. exFT may not be supported out of the box, but support can be added by installing the exfat-fuse and exfat-utils packages.
SD cards come formatted the same ways. My use for SD cards here is external data storage on Android devices. The devices can normally read the cards as formatted by the manufacturer. What I can't do with them is store on and run programs from them - FAT* filesystems have no place to store the metadata the kernel needs to run programs, like the application's owner, group, and permissions mask. (Some newer Android devices will offer to "adopt" a large capacity SD card when you insert it. If you say yes, the device will reformat the card as ext4, which is what Android uses internally. This will let you store programs on and run them from the card, but forget about trying to pop the card and reading it in something else. I played with that and decided it was more trouble for me than it was worth.)
I have no reason to format SD cards as ext4, let alone F2FS. Tell me what you want to do that might need either?
______ Dennis
Looking at the SD cards for my RPI , I was told that the best OS to put on the SD card is F2FS.
I did not know this filesytem but I have seen that it has been put in the Linux kernel and that Slackware current has the f2fs tools.
Is this filesytem realy more interesting than ext4 for SD cards ?
What did you hear ?
I don't know about this FS, but to me, whatever's being hammered the most by disk writes and reads is the only concern.
Think /var/log, swap and any other location that stores volatile data, or that serves it constantly and it's too be to be cached in RAM by the kernel.
Other than that and any metadata that the filesystem itself maintains and modifies or reads frequently, what's it matter? :-)
Thanks for your answer which is what I was thinking !
I only want to put the OS on the SD card and all the data on an USB3 key.
I wonder if the many write/read of /var /usr /swap .. is better managed by F2FS but as @drmozes said it should be better to put them into memory
Quote:
Originally Posted by DMcCunney
What will you do with the SD card?
My understanding is that FSFS is intended for solid state drives, which are a rather different animal. SSDs and SD cards are both flash media, but have different use cases and requirements.
My desktop boots from an SSD, and applications all live there. Data tends to live elsewhere. I have an assortment of USB thumbdrives that are used for backups and data I need to be portable. Those come formatted as FAT32 or exFAT, and I leave them that way. Linux can read and write FAT32 cards using the built-in support in the kernel. exFT may not be supported out of the box, but support can be added by installing the exfat-fuse and exfat-utils packages.
SD cards come formatted the same ways. My use for SD cards here is external data storage on Android devices. The devices can normally read the cards as formatted by the manufacturer. What I can't do with them is store on and run programs from them - FAT* filesystems have no place to store the metadata the kernel needs to run programs, like the application's owner, group, and permissions mask. (Some newer Android devices will offer to "adopt" a large capacity SD card when you insert it. If you say yes, the device will reformat the card as ext4, which is what Android uses internally. This will let you store programs on and run them from the card, but forget about trying to pop the card and reading it in something else. I played with that and decided it was more trouble for me than it was worth.)
I have no reason to format SD cards as ext4, let alone F2FS. Tell me what you want to do that might need either?
______ Dennis
My understanding is that FSFS is intended for solid state drives, which are a rather different animal. SSDs and SD cards are both flash media, but have different use cases and requirements.
Actually f2fs is adapted to NAND flash memory storage devices, such as SSD, eMMC, and SD cards equipped with a flash translation layer aka FTL (quoting https://www.kernel.org/doc/Documenta...stems/f2fs.txt). If the controller (that does the translation) is good enough it will protect the drive from wearing out fast, but this notwithstanding f2fs, beyond also avoiding this wearing out, is specifically adapted to these drives, thus supposed to provide better performances.
So yes, using it for an SD card is a better choice than ext4 IMO. Additionally you may want to not only count on caching by the kernel, but also have /tmp in tmpfs, and also store the cached files in your $HOME in /dev/shm/desiderius. For instance in my ~/.profile I have this code snippet:
As far as I know all desktops app work well with this setting. I also mount such file systems with noatime and nodiratime options, but I digress and you may want to know the access times
Additionally, I suggest using a fairly recent kernel, like 5.4.0_rc6 now provided in /testing as enhancements of f2fs are provided at a fast pace, even though 4.19 be OK.
Last edited by Didier Spaier; 11-08-2019 at 12:57 PM.
Reason: PS added.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.