| 1 |
On Monday, 14 December 2020 01:21:34 GMT thelma@×××××××××××.com wrote: |
| 2 |
> On 12/13/2020 05:56 PM, thelma@×××××××××××.com wrote: |
| 3 |
> > After running in "/" directory: |
| 4 |
> > touch forcefsck |
| 5 |
> > |
| 6 |
> > The file is gone now, but every time I reboot the system the root |
| 7 |
> > partition goes into force check: |
| 8 |
> > |
| 9 |
> > fstab: |
| 10 |
> > /dev/nvme0n1p4 / ext4 noatime |
| 11 |
0 1 |
| 12 |
> |
| 13 |
> If I'm not mistaken it should be: |
| 14 |
> |
| 15 |
> tune2fs -c -1 /dev/nvme0n1p4 |
| 16 |
> |
| 17 |
> but why was the setting reset when I run "touch forcefsck" |
| 18 |
|
| 19 |
Use 'tune2fs -l /dev/nvme0n1p4' to see what settings the fs superblock |
| 20 |
contains and in particular check the 'Maximum mount count' and 'Check |
| 21 |
interval' values. These can be set to your liking. |
Archives