Oops didn't send the mail to the mailinglist, so I will resend. Hi > > Thanks for your help. > I have another request: > > # dumpseg /dev/loop1 12
r...@robin-laptop:/tmp# dumpseg /dev/loop1 12
segment: segnum = 12
partial segment
creation time = 2008-12-26 11:45:06
nfinfo = 0
>
> - This will dump the summary of the segment in question
>
> # dd if=/dev/loop1 bs=4k skip=24576 count=2 | hd
>
> - This will dump the (broken) root block of the file system
>
Ok I atached it to the email bzip2 compressed
> According to your log, the btree root of DAT file (i.e. a table file
> to translate disk addresses) seems inconsistent. It might not be
> updated properly when GC moved its blocks. I suspect that it was
> caused by some sort of GC problem.
>
> And, your nilfs partition seems to have shut down uncleanly before
> this mount error repeatedly happened. Do you remember what the first
> trouble was like?
>
Actualy I have no real idea. Didn't start the computer for some days over
christmas, befor christmas I could use the filesystem withoul any trouble, and
on december 26 I was unable to mount it.
I actualy quite often moved files of the nilfs filesystem to an USB stick.
Using comands like
"mv /mnt/nilfs/directory/*.avi /mnt/usb && poweroff". So there were some
shutdowns I didn't watch, and I was thinking that the normal shutdown scripts
should unmount every mounted filesystem. Well the computer was definitv off,
but I have no idea if it could be possible that something importend was stoped
to soon when it came to the point "sending all procecess the term signal"
> Regards,
> Ryusuke
>
robinx99
hd.bz2
Description: Binary data
_______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
