Your message dated Tue, 18 Feb 2014 09:54:57 -0700
with message-id <[email protected]>
and subject line Re: Bug#739155: util-linux: fsck is broken
has caused the Debian Bug report #739155,
regarding util-linux: fsck is broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
739155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739155
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: util-linux
Version: 2.20.1-5.3
Severity: minor

Dear Maintainer,

after a kernel panic (related to udev) the system wanted to fsck all 
filesystems. First the rootfs was checked:

> cat /var/log/fsck/checkroot 
Log of fsck -C -a -t ext3 /dev/sda4 
Sun Feb 16 10:07:14 2014

fsck from util-linux 2.20.1
/dev/sda4: clean, 26581/610800 files, 269861/2441472 blocks

Sun Feb 16 10:07:15 2014
----------------
The the other filesystems should be checked but fsck died when checking
sda4 again:
> cat /var/log/fsck/checkfs   
Log of fsck -C -R -A -a 
Sun Feb 16 10:07:15 2014

fsck from util-linux 2.20.1
/dev/sda2: clean, 27/31232 files, 11494/62464 blocks
/dev/sda4 is mounted.
e2fsck: Cannot continue, aborting.


fsck died with exit status 8

Sun Feb 16 10:07:15 2014
----------------

Here are the corresponding lines from the fstab:

/dev/sda4       /       ext3    errors=remount-ro       0       1
/dev/sda2       /boot   ext2    defaults                0       2
/dev/sda1       /boot/efi       vfat    defaults        0       1
/dev/sda4       /opt    ext4    defaults                0       2
/dev/sda3       none    swap    sw                      0       0

It looks as the -R option to fsck is not working of fsck is unable 
to recognise the rootfs when it is mounted.

> mount | grep " / "
/dev/block/8:4 on / type ext3 
(rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)

> cat /proc/mounts | grep " / "
rootfs / rootfs rw 0 0
/dev/block/8:4 / ext3 
rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered 0 0

Regards,
Stephan

-- System Information:
Debian Release: 7.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages util-linux depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  dpkg                   1.16.12
ii  initscripts            2.88dsf-41+deb7u1
ii  install-info           4.13a.dfsg.1-10
ii  libblkid1              2.20.1-5.3
ii  libc6                  2.13-38+deb7u1
ii  libncurses5            5.9-10
ii  libselinux1            2.1.9-5
ii  libslang2              2.2.4-15
ii  libtinfo5              5.9-10
ii  libuuid1               2.20.1-5.3
ii  lsb-base               4.1+Debian8+deb7u1
ii  tzdata                 2013i-0wheezy1
ii  zlib1g                 1:1.2.7.dfsg-13

util-linux recommends no packages.

Versions of packages util-linux suggests:
pn  dosfstools          <none>
ii  kbd                 1.15.3-9
pn  util-linux-locales  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Closing per the submitter

lamont
----- Forwarded message from "[email protected]" 
<[email protected]> -----

Date: Sun, 16 Feb 2014 10:55:48 +0100
From: "[email protected]" <[email protected]>
To: LaMont Jones <[email protected]>
Subject: Bug  #739155 submitted by myself
X-Mailer: DTAG LISA 0.1

Dear LaMont,
please mark my bugreport as solved oder something matching. 
I found the reason for this bug ... I have /dev/sda4 twice in the fstab 
und the second entrie is a typo and should have been sda5.
Sorry for disturbing.
Best regards,
Stephan


----- End forwarded message -----

--- End Message ---

Reply via email to