what are the messages below for which i get when reboot with /forcefsck
at least on kernel 4.10.7?
___________________________________________________
and no, i can't unmount the device because after repeated "umount
/dev/md2" which are unmounting some bind-mounts i get the following
message while nothing (lsof, fuser with all sort of options) shows any
open filehandle and all processes are stopped - so no way just enter
"fsck" with params and that issue exists for years
target is busy (In some cases useful info about processes that use the
device is found by lsof(8) or fuser(1).
___________________________________________________
Mar 31 12:55:40 rh systemd-fsck: system: clean, 214548/1921360 files,
1888521/7679232 blocks
Mar 31 12:55:43 rh systemd-fsck: Please pass 'fsck.mode=force' on the
kernel command line rather than creating /forcefsck on the root file system.
Mar 31 12:55:43 rh systemd-fsck: Please pass 'fsck.mode=force' on the
kernel command line rather than creating /forcefsck on the root file system.
Mar 31 12:55:43 rh systemd-fsck: boot: 375/128016 Dateien (1.3% nicht
zusammenhängend), 50000/511988 Blöcke
Mar 31 12:55:47 rh systemd-fsck: data: Inode 14681437 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:47 rh systemd-fsck: data: Inode 15073688 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:47 rh systemd-fsck: data: Inode 15991040 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:48 rh systemd-fsck: data: Inode 17170787 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:48 rh systemd-fsck: data: Inode 18088064 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:49 rh systemd-fsck: data: Inode 21758420 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:50 rh systemd-fsck: data: Inode 22675780 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:50 rh systemd-fsck: data: Inode 23855220 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:50 rh systemd-fsck: data: Inode 24642524 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:51 rh systemd-fsck: data: Inode 25821208 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:51 rh systemd-fsck: data: Inode 28312065 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:52 rh systemd-fsck: data: Inode 29229111 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:52 rh systemd-fsck: data: Inode 31326708 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:53 rh systemd-fsck: data: Inode 33030483 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:53 rh systemd-fsck: data: Inode 35127422 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:54 rh systemd-fsck: data: Inode 36962716 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:54 rh systemd-fsck: data: Inode 37749004 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:55:59 rh systemd-fsck: data: Inode 40108093 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:56:00 rh systemd-fsck: data: Inode 40894470 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:56:01 rh systemd-fsck: data: Inode 52822304 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:56:03 rh systemd-fsck: data: Inode 63045758 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:56:06 rh systemd-fsck: data: Inode 108790765 Erweiterung tree
(at level 1) could be shorter. IGNORIERT.
Mar 31 12:56:08 rh systemd-fsck: data: Inode 162529337 Erweiterung tree
(at level 1) could be narrower. IGNORIERT.
Mar 31 12:56:08 rh systemd-fsck: data: Inode 162531692 Erweiterung tree
(at level 1) could be narrower. IGNORIERT.
Mar 31 12:56:51 rh systemd-fsck: data: 745984/242204672 Dateien (0.7%
nicht zusammenhängend), 193226508/968805632 Blöcke
On Fri, Mar 31, 2017 at 01:30:18PM +0200, Reindl Harald wrote:
> what are the messages below for which i get when reboot with /forcefsck at
> least on kernel 4.10.7?
> ___________________________________________________
>
> and no, i can't unmount the device because after repeated "umount /dev/md2"
> which are unmounting some bind-mounts i get the following message while
> nothing (lsof, fuser with all sort of options) shows any open filehandle and
> all processes are stopped - so no way just enter "fsck" with params and that
> issue exists for years
Some services ask systemd to run in their own private fs namespaces
(ProtectSystem=true) and so even though you umount the fs in the regular
namespace that doesn't unmount the fs in the private namespace, which
means that e2fsck & friends report that the fs is still mounted. You
can find out if this is the case by grepping for the mountpoint in
/proc/*/mounts after unmounting the fs from the shell.
(And yes, this, uh, quirk has visited me many times.)
> target is busy (In some cases useful info about processes that use the
> device is found by lsof(8) or fuser(1).
> ___________________________________________________
>
> Mar 31 12:55:40 rh systemd-fsck: system: clean, 214548/1921360 files,
> 1888521/7679232 blocks
> Mar 31 12:55:43 rh systemd-fsck: Please pass 'fsck.mode=force' on the kernel
> command line rather than creating /forcefsck on the root file system.
> Mar 31 12:55:43 rh systemd-fsck: Please pass 'fsck.mode=force' on the kernel
> command line rather than creating /forcefsck on the root file system.
> Mar 31 12:55:43 rh systemd-fsck: boot: 375/128016 Dateien (1.3% nicht
> zusammenh?ngend), 50000/511988 Bl?cke
> Mar 31 12:55:47 rh systemd-fsck: data: Inode 14681437 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
My ability to interpret "deutschglish" isn't all that good, but I'm
pretty sure this is e2fsck complaining about unnecessarily large and
sparse extent trees, though it's clearly not optimizing them.
--D
> Mar 31 12:55:47 rh systemd-fsck: data: Inode 15073688 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:47 rh systemd-fsck: data: Inode 15991040 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:48 rh systemd-fsck: data: Inode 17170787 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:48 rh systemd-fsck: data: Inode 18088064 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:49 rh systemd-fsck: data: Inode 21758420 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:50 rh systemd-fsck: data: Inode 22675780 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:50 rh systemd-fsck: data: Inode 23855220 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:50 rh systemd-fsck: data: Inode 24642524 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:51 rh systemd-fsck: data: Inode 25821208 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:51 rh systemd-fsck: data: Inode 28312065 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:52 rh systemd-fsck: data: Inode 29229111 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:52 rh systemd-fsck: data: Inode 31326708 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:53 rh systemd-fsck: data: Inode 33030483 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:53 rh systemd-fsck: data: Inode 35127422 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:54 rh systemd-fsck: data: Inode 36962716 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:54 rh systemd-fsck: data: Inode 37749004 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:55:59 rh systemd-fsck: data: Inode 40108093 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:56:00 rh systemd-fsck: data: Inode 40894470 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:56:01 rh systemd-fsck: data: Inode 52822304 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:56:03 rh systemd-fsck: data: Inode 63045758 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:56:06 rh systemd-fsck: data: Inode 108790765 Erweiterung tree (at
> level 1) could be shorter. IGNORIERT.
> Mar 31 12:56:08 rh systemd-fsck: data: Inode 162529337 Erweiterung tree (at
> level 1) could be narrower. IGNORIERT.
> Mar 31 12:56:08 rh systemd-fsck: data: Inode 162531692 Erweiterung tree (at
> level 1) could be narrower. IGNORIERT.
> Mar 31 12:56:51 rh systemd-fsck: data: 745984/242204672 Dateien (0.7% nicht
> zusammenh?ngend), 193226508/968805632 Bl?cke
Am 31.03.2017 um 18:19 schrieb Darrick J. Wong:
> On Fri, Mar 31, 2017 at 01:30:18PM +0200, Reindl Harald wrote:
>> what are the messages below for which i get when reboot with /forcefsck at
>> least on kernel 4.10.7?
>> ___________________________________________________
>>
>> and no, i can't unmount the device because after repeated "umount /dev/md2"
>> which are unmounting some bind-mounts i get the following message while
>> nothing (lsof, fuser with all sort of options) shows any open filehandle and
>> all processes are stopped - so no way just enter "fsck" with params and that
>> issue exists for years
>
> Some services ask systemd to run in their own private fs namespaces
> (ProtectSystem=true) and so even though you umount the fs in the regular
> namespace that doesn't unmount the fs in the private namespace, which
> means that e2fsck & friends report that the fs is still mounted. You
> can find out if this is the case by grepping for the mountpoint in
> /proc/*/mounts after unmounting the fs from the shell.
>
> (And yes, this, uh, quirk has visited me many times.)
but my *data* partition when all services are stopped which would have
namespaces there for ReadOnly/ReadWrite/Deny?
some "umount --force" would be really cool since after "systemctl
isolate rescue.target" that all should be gone
>> target is busy (In some cases useful info about processes that use the
>> device is found by lsof(8) or fuser(1).
>> ___________________________________________________
>>
>> Mar 31 12:55:40 rh systemd-fsck: system: clean, 214548/1921360 files,
>> 1888521/7679232 blocks
>> Mar 31 12:55:43 rh systemd-fsck: Please pass 'fsck.mode=force' on the kernel
>> command line rather than creating /forcefsck on the root file system.
>> Mar 31 12:55:43 rh systemd-fsck: Please pass 'fsck.mode=force' on the kernel
>> command line rather than creating /forcefsck on the root file system.
>> Mar 31 12:55:43 rh systemd-fsck: boot: 375/128016 Dateien (1.3% nicht
>> zusammenh?ngend), 50000/511988 Bl?cke
>> Mar 31 12:55:47 rh systemd-fsck: data: Inode 14681437 Erweiterung tree (at
>> level 1) could be shorter. IGNORIERT.
>
> My ability to interpret "deutschglish" isn't all that good, but I'm
> pretty sure this is e2fsck complaining about unnecessarily large and
> sparse extent trees, though it's clearly not optimizing them
oh, no nothing really bad