On 2/16/15 4:30 AM, Reindl Harald wrote: > /dev/sda1 is a ordinary partition containing only /boot > why does the kernel report it is in use? > if that would be true it could not be unmounted > ___________________________________________ > > [root@asterisk:~]$ /usr/sbin/fsck.ext4 -f /dev/sda1 > e2fsck 1.42.12 (29-Aug-2014) > /dev/sda1 is in use. > e2fsck: Cannot continue, aborting. I just saw a similar report on #ext4; do you still have a jbd thread running for this filesystem? Also, in the spirit of useful bug reporting, what kernel are you running? Can you run strace of e2fsck, and see if an open(O_EXCL) fails, or find some other hint about how e2fsck decided it was in use? Possibly paste the last couple hundred lines of strace somewhere. This may be better suited for a bug report, or a thread on linux-ext4, than the fedora-kernel list. FWIW, the errors below do look indicative of a filesystem that has never had the superblock written out during an actual unmount... Thanks, -Eric ________________________________________ > > [root@asterisk:~]$ lsof | grep /dev/sda1 > [root@asterisk:~]$ > ___________________________________________ > > [root@asterisk:~]$ /usr/sbin/fsck.ext4 -n /dev/sda1 > e2fsck 1.42.12 (29-Aug-2014) > Warning! /dev/sda1 is in use. > boot was not cleanly unmounted, check forced. > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > Free blocks count wrong (454751, counted=469570). > Fix? no > > Free inodes count wrong (130215, counted=130220). > Fix? no > > boot: 345/130560 files (22.6% non-contiguous), 66464/521215 blocks > > > > _______________________________________________ > kernel mailing list > kernel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/kernel > _______________________________________________ kernel mailing list kernel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kernel
