I'm just pasting the lines from bootmsg:
<4>[ 44.155713] systemd-fsck[269]: fsck.jfs version 1.1.14, 06-Apr-2009 <4>[ 44.155760] systemd-fsck[269]: processing started: 10/29/2010 18.53.14 <4>[ 44.155796] systemd-fsck[269]: /dev/ida/c0d0p3 is mounted. <4>[ 44.155830] systemd-fsck[269]: WARNING!!! <4>[ 44.155865] systemd-fsck[269]: Running fsck on a mounted file system <4>[ 44.155901] systemd-fsck[269]: may cause SEVERE file system damage. <4>[ 44.155937] systemd-fsck[269]: Do you really want to continue (y/n)? no <4>[ 44.155972] systemd-fsck[269]: Check aborted.
On Fri, 2010-10-29 at 19:11 +0200, Per Jessen wrote:
I'm just pasting the lines from bootmsg:
<4>[ 44.155713] systemd-fsck[269]: fsck.jfs version 1.1.14, 06-Apr-2009 <4>[ 44.155760] systemd-fsck[269]: processing started: 10/29/2010 18.53.14 <4>[ 44.155796] systemd-fsck[269]: /dev/ida/c0d0p3 is mounted. <4>[ 44.155830] systemd-fsck[269]: WARNING!!! <4>[ 44.155865] systemd-fsck[269]: Running fsck on a mounted file system <4>[ 44.155901] systemd-fsck[269]: may cause SEVERE file system damage. <4>[ 44.155937] systemd-fsck[269]: Do you really want to continue (y/n)? no <4>[ 44.155972] systemd-fsck[269]: Check aborted.
Yeah, I'm currently fixing this. It's because the SUSE initramfs leaves the rootfs mounted r/w, which is pretty unusal. We'll need to skip the systemd native fsck when the filesystem is already r/w.
Kay
Hi;
On Fri, Oct 29, 2010 at 8:22 PM, Kay Sievers kay.sievers@suse.de wrote:
On Fri, 2010-10-29 at 19:11 +0200, Per Jessen wrote:
I'm just pasting the lines from bootmsg:
<4>[ 44.155713] systemd-fsck[269]: fsck.jfs version 1.1.14, 06-Apr-2009 <4>[ 44.155760] systemd-fsck[269]: processing started: 10/29/2010 18.53.14 <4>[ 44.155796] systemd-fsck[269]: /dev/ida/c0d0p3 is mounted. <4>[ 44.155830] systemd-fsck[269]: WARNING!!! <4>[ 44.155865] systemd-fsck[269]: Running fsck on a mounted file system <4>[ 44.155901] systemd-fsck[269]: may cause SEVERE file system damage. <4>[ 44.155937] systemd-fsck[269]: Do you really want to continue (y/n)? no <4>[ 44.155972] systemd-fsck[269]: Check aborted.
Yeah, I'm currently fixing this. It's because the SUSE initramfs leaves the rootfs mounted r/w, which is pretty unusal. We'll need to skip the systemd native fsck when the filesystem is already r/w.
Just out of curiosity, is there any reason for mounting initramfs as r/w?
Regards, ismail
On Fri, 2010-10-29 at 20:26 +0300, İsmail Dönmez wrote:
Hi;
On Fri, Oct 29, 2010 at 8:22 PM, Kay Sievers kay.sievers@suse.de wrote:
On Fri, 2010-10-29 at 19:11 +0200, Per Jessen wrote:
I'm just pasting the lines from bootmsg:
<4>[ 44.155713] systemd-fsck[269]: fsck.jfs version 1.1.14, 06-Apr-2009 <4>[ 44.155760] systemd-fsck[269]: processing started: 10/29/2010 18.53.14 <4>[ 44.155796] systemd-fsck[269]: /dev/ida/c0d0p3 is mounted. <4>[ 44.155830] systemd-fsck[269]: WARNING!!! <4>[ 44.155865] systemd-fsck[269]: Running fsck on a mounted file system <4>[ 44.155901] systemd-fsck[269]: may cause SEVERE file system damage. <4>[ 44.155937] systemd-fsck[269]: Do you really want to continue (y/n)? no <4>[ 44.155972] systemd-fsck[269]: Check aborted.
Yeah, I'm currently fixing this. It's because the SUSE initramfs leaves the rootfs mounted r/w, which is pretty unusal. We'll need to skip the systemd native fsck when the filesystem is already r/w.
Just out of curiosity, is there any reason for mounting initramfs as r/w?
No idea why the SUSE initramfs mounts / as r/w. There is nothing wrong with it, it's just unusual. I never even noticed that before. :)
Kay
On Fri, 2010-10-29 at 19:22 +0200, Kay Sievers wrote:
On Fri, 2010-10-29 at 19:11 +0200, Per Jessen wrote:
I'm just pasting the lines from bootmsg:
<4>[ 44.155713] systemd-fsck[269]: fsck.jfs version 1.1.14, 06-Apr-2009 <4>[ 44.155760] systemd-fsck[269]: processing started: 10/29/2010 18.53.14 <4>[ 44.155796] systemd-fsck[269]: /dev/ida/c0d0p3 is mounted. <4>[ 44.155830] systemd-fsck[269]: WARNING!!! <4>[ 44.155865] systemd-fsck[269]: Running fsck on a mounted file system <4>[ 44.155901] systemd-fsck[269]: may cause SEVERE file system damage. <4>[ 44.155937] systemd-fsck[269]: Do you really want to continue (y/n)? no <4>[ 44.155972] systemd-fsck[269]: Check aborted.
Yeah, I'm currently fixing this. It's because the SUSE initramfs leaves the rootfs mounted r/w, which is pretty unusal. We'll need to skip the systemd native fsck when the filesystem is already r/w.
Should be fixed: http://cgit.freedesktop.org/systemd/commit/?id=a84f519214bf245052ad6be7b57fb...
Kay
-
İsmail Dönmez -
Kay Sievers -
Per Jessen