xfs_repair stops on "traversing filesystem..."

[Eric Sandeen]

Tomek Kruszona wrote:

...

> I made some tests and it seems, that filesystem to finish xfs_repair
> needs to be repaired with bhash=1024... With default options it still
> hangs on "traversing filesystem..." Is it possible to change this
> behavior to normal in other way than reformat? 

It has nothing to do w/ the format, it's just internal to xfs_repair
while it's running, the way it caches blocks that it has recently used.

> Moreover I spotted some
> strange thing. 16GB of data has been moved to lost+found. I tried to

Yeah ...

> clean L+F by
> # rm -rf lost+found
> 
> but suddenly I got this:
> 
> # ls -l /mnt/storage/
> ls: cannot access /mnt/storage/lost+found: No such file or directory
> total 0
> drwxr-xr-x 4 root    root 33 Mar  4 17:21 l_mirror
> ?????????? ? ?       ?     ?            ? lost+found

huh.  let me try on the repaired metadata image...

[root at bear-05 bad-repair]# mount -o loop badfs.img mnt/
[root at bear-05 bad-repair]# du -hc mnt/lost+found/
26M	mnt/lost+found/1602304
5.0M	mnt/lost+found/2558868
18G	mnt/lost+found/
18G	total
[root at bear-05 bad-repair]# rm -rf mnt/lost+found/*
[root at bear-05 bad-repair]# ls -l mnt/
total 0
drwxr-xr-x 4 root root 33 Mar  4 10:21 ??5?t??4
drwxr-xr-x 0 root root  6 Jul 10 19:48 lost+found
drwxr-xr-x 2 1000 root  6 Jun 30 08:45 tests

Did you do something else to the fs in between?

> I had to run xfs_repair (bhash=1024) once again and then l+f disappeared...
> 
> So I started to think: does it have some influence on data that are
> stored on this filesystem? I'm afraid that files on this FS may become
> inconsistent :/

Well, I don't know what has gone wrong with your filesytem (or, with the
storage beneath it, or whatever) - but it is certainly possible that
with corrupted metadata, that there is corrupted data as well - all
depends on the root cause ...

-Eric

> Best regards,
> Tomasz Kruszona