On 28/10/24 09:28, ToddAndMargo via
users wrote:
On 10/27/24 14:20, Stephen Morris wrote:
On 27/10/24 13:37, ToddAndMargo via users wrote:
On 10/26/24 18:10, Samuel Sieb wrote:If you are mounting your partitions via fstab, for the last 2 parameters on your mount definition you can specify 0 1 for the root partition and 0 2 for all other partitions. The 0 specifies to not dump the volume the 1 or 2 specifies to do an fsck at mount time. The man page says to specify 1 for the root volume and 2 for all other volume to utilise hardware parallelism if available, also with 1 specified for the root volume that will be checked first.
On 10/26/24 6:01 PM, ToddAndMargo via users wrote:
On 10/26/24 17:55, Samuel Sieb wrote:
On 10/26/24 5:40 PM, ToddAndMargo via users wrote:
On 10/26/24 17:29, ToddAndMargo via users wrote:
The tune2fs command is used to modify the filesystem mount options and settings for ext2, ext3, and ext4 file systems. The option -E force_fsck enables forced filesystem checks (fsck) on every reboot, while the repair option specifies that fsck should attempt to automatically repair any issues found during the check.
# tune2fs -E force_fsck repair /dev/mapper/luks-903bc691- a0f0-42bc- aa96-4233a7edc0e9
tune2fs 1.47.0 (5-Feb-2023)
Usage: tune2fs ...
What did I do wrong?
Where did that "repair" thing come from? The flag you're setting is called "force_fsck".
https://search.brave.com/search?q=tune2fs+- E+force_fsck+repair&summary=1&summary_og=5ad6fac8ba3b05432c1504
Tune2fs Force FSCK Repair
The tune2fs command is used to modify the filesystem mount options and settings for ext2, ext3, and ext4 file systems. The option -E force_fsck enables forced filesystem checks (fsck) on every reboot, while the repair option specifies that fsck should attempt to automatically repair any issues found during the check.
AI answers... Apparently I got a slightly different one than you.
"The repair part of the command is not a separate option, but rather a concept."
In an earlier message you said "it did run". What was "it" that took 10 seconds?
fsck ran at boot, but only took about 10 seconds for a
1TB drive. I am doubtful it tried tp do a repair.
If it found something, it would have repaired it or indicated a problem.
That command just sets the flag. You either need to reboot or remount the filesystem after setting it. Although if you can unmount it, then you don't need to set the flag. You could just run "e2fsck" directly.
It is my / partition. I suppose I could run a live usb and do
a repair from there?
I would recommend that if you are doubting the current situation.
I am not having any luck finding for to tell e2fsck I want a
repair too.
Because there is no distinction. That flag marks the filesystem as having errors, so it needs to be checked when mounted. However, I'm not sure that the mounting fsck is as thorough as a manually run one. I actually think that if it finds any non-trivial issue that it will just fail the mount. So do try that live boot.
Thank you! I was over thinking it.
regards,
Steve
My fstab
dev/mapper/luks-903bc691-a0f0-42bc-aa96-4233a7edc0e9 / ext4 defaults,x-systemd.device-timeout=0 1 1
UUID=f3edab67-2614-4c23-a4d1-fc78b37d74f3 /boot ext4 defaults 1 2
UUID=3E81-B783 /boot/efi vfat umask=0077,shortname=winnt 0 2
/dev/mapper/luks-c72067fc-1742-4628-affc-f80b14974beb swap swap defaults,x-systemd.device-timeout=0 0 0
#
/dev/sr0 /mnt/sr0 auto ro,users,noauto,unhide 0 0
Based on the man info for fstab I would expect the first 3 mount points to be checked at mount time, hence a manual process shouldn't be required. What I'm not sure of at the moment, because there doesn't seem to be any feedback at boot time, unlike Ubuntu, is where the feedback from the check is written to.
regards,
Steve
Attachment:
OpenPGP_0x1EBE7C07B0F7242C.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
