El 7/10/25 a las 16:04, Dale escribió:
Howdy,As most everyone knows, I have some large file systems here. Mostly videos. These are encrypted until I open/unlock them. So, when I am on those rare occasions booting up, there's no way to run fsck on them automatically. I basically have two questions on this. 1: How often should I open but not mount the file system and run fsck on it? Once a month, two months, six months, a year or what. 2: Also, what is a command that you use that will fix most things without asking a lot of questions but not do anything that will damage or potentially damage a file? Basically, what command would you use for a situation like this? The man page shows a option for all 'yes' but there may be times when 'yes' isn't a good idea. I'm wondering if someone has came up with a way to handle this with some option I'm not aware of. Right now I use the command e2fsck -pf /dev/mapper/<mount point here> to check it but it ignores some things that it would usually fix if I were being asked first. Something about things could be smaller. It's usually a LOT of them. I'd like those to be corrected as well. Maybe running the check twice with different options will fix it all???? Current info. FILESYSTEM (=) USED FREE (-) %USED USED AVAILABLE TOTAL MOUNTED ON /dev/mapper/crypt [==========================================--------] 83.8% 39.5T 7.6T 47.1T /home/dale/Desktop/Crypt /dev/mapper/data [==============================================----] 91.7% 43.2T 3.9T 47.1T /home/dale/Desktop/Data I'm thinking about adding a 18 or 20TB drive to data. I got a empty one in my safe as a spare. May need to buy a couple more drives soon. Thanks. Dale :-) :-)
You can make one script involving cryptsetup and fsck. Or you can add one passfile to the luks volume add it to the crypttab and to the fstab to auto unlock at booting and check it.
I suggest you that you make the check every time you are going to mount your disk before doing it. If the filesystem has some kind of error could be problematic. If its in healthy state, it will not spend time,
Maybe you can use "-E no_optimize_extents" option in e2fsck if the message that is boring you is related with extents optimization.
OpenPGP_0x57E64E0B7FC3BEDF.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
