bedrock, fstrim
 

At the moment all of my partitions except for /boot are on a thin provisioned LVM. Is it safe to run fstrim on bedrock?

Thank you.

I don't see why Bedrock would be a factor in such a decision.

So, fstrim has no problem interactions with etcfs, crossfs or any other bedrock bits?

A bit of caution for things seems appropriate, so hence my original question.

So far I've only been performing fstrim on the bedrock partition when booted off of one of the other OS's.

Thank you.

Ah, I think I see: you're concerned about etcfs and crossfs and fstrim all share "fs" - filesystem - in their names, and thus may be related.

etcfs and crossfs work on the virtual filesystem layer, not the block layer. They operate the same as utilities like ls and cat, agnostic to the underlying hardware or filesystem. etcfs and crossfs are referred to as filesystems because of how the user interacts with them, and not because of how they interact with the hardware.

If you run `cat /home/dobbs/.config/vlc/vlcrc`, cat's request goes to the kernel, which does some work then returns the results to cat. The kernel is abstracting the underlying hardware and filesystem. cat doesn't know or care if it's reading from ext4 or btrfs, from a spinny harddrive or an SSD, with or without trim enabled.

If you `cat /bedrock/cross/applications/vlc.desktop`, the request goes to the kernel, which does some work and returns the result to cat. The difference is here, that work involves asking crossfs what to do. crossfs reads some files to figure it out. When it does so, the request goes to the kernel - same as with cat. The kernel abstracts the underlying hardware and filesystem from crossfs, too. crossfs doesn't know or care if it's reading from ext4 or btrfs, from a spinny harddrive or an SSD, with or without trim enabled.

Just like ls and cat, etcfs and crossfs do not care about trim or not trim. They operate at a different level of abstraction.

Just now, I ran fstrim via the way I'd done it in previous distros:
It didn't do the / partition. Most unexpected. That's a new one on me. Also, after /hsc and before /home, there was a pause or hesitation of almost a minute. That was also unexpected.

Ran it a different way:
That time it did the slash partition and also it seemed to run much faster. The distinction between -a (currently mounted devices that can discard) and -A (devices in fstab that can discard) seems subtle to me but apparently isn't.