Print Page - fsck fails after du

Title: fsck fails after du
Post by: bad_aptitude on 2013/05/28, 05:56:54

After a du today my boot sequence stops at the fsck. My root file system is set to "read only" and the system suggests that I do a "manual" fsck.
If I press "ctrl D" to continue the system just shuts down. If I enter the repair shell by entering the root password and run fsck I just get the BTRFS help menu.
My root file system is BTRFS.
Running older kernels doesn't help. Is there a way pass this impasse?

Title: RE: fsck fails after du
Post by: timc on 2013/05/28, 13:44:29

It is a bug. You need to edit your fstab so that it does not try to fsck your root filesystem. I will post more info as I can gather it.

Tim

Title: RE: fsck fails after du
Post by: timc on 2013/05/28, 13:46:45

First, see this thread:

http://forum.siduction.org/index.php?topic=3251&highlight=

Tim

Title: RE: fsck fails after du
Post by: timc on 2013/05/28, 13:59:18

To mount the root filesystem as rw during bootup:

Code Select

mount -o remount,rw /

Tim

Title: fsck fails after du
Post by: bad_aptitude on 2013/05/29, 06:19:56

Thanks Tim.
I have a separate BTRFS LVM for /home so I had to edit fstab for it too.

I wonder when it will be fixed?

Title: fsck fails after du
Post by: timc on 2013/05/29, 13:37:33

Quote from: "bad_aptitude"Thanks Tim.

...

I wonder when it will be fixed?

I'm not sure, but I saw some discussion of it in the btrfs mail list a week or so ago.

Tim

Title: fsck fails after du
Post by: bad_aptitude on 2013/05/29, 22:06:05

I wonder IF it should be fixed? ;)
According to: https://btrfs.wiki.kernel.org/index.php/FAQ
and I quote:
"Traditional filesystems need to run their respective fsck utility in case the filesystem was not unmounted cleanly and the log needs to be replayed before mount. This is not needed for btrfs. You should set fs_passno to 0."

Siduction Forum

Siduction Forum => Upgrade Warnings => Topic started by: bad_aptitude on 2013/05/28, 05:56:54