/forcefsck is obsolete
Modern file systems are expected to determine themselves if fsck is
needed. XFS, ext4, btrfs, all can do log replay at mount time and that
fixes the vast majority of problems. On XFS and Btrfs, if log replay
has problems, mount will fail and it's expected the user manually r
Allegedly, on or about 6 August 2017, Ahmad Samir sent:
> The root / filesystem isn't force-checked with /forcefsck; you'd have
> to use fsck.mode=force kernel boot parameter. I tested that on a
> clean
> install in a vm. The other filesystems listed in fsck are checked
> AFAICS.
>
> systemd is de
> The root / filesystem isn't force-checked with /forcefsck; you'd have
> to use fsck.mode=force kernel boot parameter. I tested that on a clean
> install in a vm. The other filesystems listed in fsck are checked
> AFAICS.
Yes, I discovered that. All my filesystems were checked apart from /!
Fréd
On 5 August 2017 at 06:50, Samuel Sieb wrote:
> On 08/04/2017 06:46 AM, Mamoru TASAKA wrote:
>>
>> Touching /forcefsck was for sysvinit and upstart era. It is no longer
>> valid
>> for systemd.
>
>
> This is still valid and has nothing to do with systemd. It's handled by
> dracut in the initramfs
On 5/8/2017 2:35 pm, Samuel Sieb wrote:
It used to have a value, but it was not that helpful and could be quite
annoying.
Back when hard drives were small, the occasional fsck was somewhat
annoying. I'd really hate to be stuck waiting while the computer checks
through a 500 GB drive, just fo
On 08/04/2017 09:54 PM, Frédéric Bron wrote:
Yes, apparently from the last checked date, it seems that /forcefsck
worked but I was expecting to see something on the screen and it must
be done hidden.
Unless there's a problem, it will run very quickly.
___
On 08/04/2017 09:59 PM, Frédéric Bron wrote:
Apparently the default value is -1 on my partitions which according to
the manual means "If max-mount-counts is 0 or -1, the number of times
the filesystem is mounted will be disregarded by e2fsck(8) and the
kernel."
So I guess that fsck is then ran o
> sudo tune2fs -c 50 /dev/[your dev]
>
> the -c option set the interval of boots. Change it to 1 and it will check
> every boot... 30 I believe is the current default because every boot is
> impractical imo. I believe you can set the priority in the fstab.. last
> column if memory serves. 0 no c
>> Touching /forcefsck was for sysvinit and upstart era. It is no longer
>> valid
>> for systemd.
>
> This is still valid and has nothing to do with systemd. It's handled by
> dracut in the initramfs.
Yes, apparently from the last checked date, it seems that /forcefsck
worked but I was expecting
>>Apparently, this does not work:
>># tune2fs -l /dev/sda
>>tune2fs 1.43.3 (04-Sep-2016)
>>tune2fs: Bad magic number in super-block while trying to open /dev/sda
>>Found a gpt partition table in /dev/sda
>
> /dev/sda is usually a drive name, not a partition name. Does it work if you
> try /dev/sd
On 08/04/2017 06:46 AM, Mamoru TASAKA wrote:
Touching /forcefsck was for sysvinit and upstart era. It is no longer valid
for systemd.
This is still valid and has nothing to do with systemd. It's handled by
dracut in the initramfs.
___
users mailing
On 08/03/2017 11:05 PM, fred roller wrote:
I believe you could use tune2fs command
sudo tune2fs -c 50 /dev/[your dev]
the -c option set the interval of boots. Change it to 1 and it will
check every boot... 30 I believe is the current default because every
boot is impractical imo. I believe
>Apparently, this does not work:
># tune2fs -l /dev/sda
>tune2fs 1.43.3 (04-Sep-2016)
>tune2fs: Bad magic number in super-block while trying to open /dev/sda
>Found a gpt partition table in /dev/sda
/dev/sda is usually a drive name, not a partition name. Does it work if you
try /dev/sda1 or /dev
> It probably ran and you didn't see it. For ext2/3/4, you can run
>tune2fs -l /dev/{whatever} | grep "Last checked"
Apparently, this does not work:
# tune2fs -l /dev/sda
tune2fs 1.43.3 (04-Sep-2016)
tune2fs: Bad magic number in super-block while trying to open /dev/sda
Found a gpt partition t
Frédéric Bron wrote on 08/04/2017 02:05 PM:
I would like to force fsck at boot but I tried touch /forcefsck and it
did not run or I did not see it (however the file /forcefsck
disappeared).
Thanks,
Frédéric
Add the following to the boot parameter:
fsck.mode=force
Touching /forcefsck was for sy
On 08/04/2017 12:05 AM, Frédéric Bron wrote:
I would like to force fsck at boot but I tried touch /forcefsck and it
did not run or I did not see it (however the file /forcefsck
disappeared).
It probably ran and you didn't see it. For ext2/3/4, you can run
tune2fs -l /dev/{whatever} | grep "
I believe you could use tune2fs command
sudo tune2fs -c 50 /dev/[your dev]
the -c option set the interval of boots. Change it to 1 and it will check
every boot... 30 I believe is the current default because every boot is
impractical imo. I believe you can set the priority in the fstab.. last
co
17 matches
Mail list logo
