Re: Still some corruption occurs on my root filesystem

[Michael Wahlbrink <x_miw@propack-data.com>]

Hi again,
Willi Langenberger wrote:
> According to Michael Wahlbrink:
> 
>>It was a normal shutdown, :-(
>>...and it also did't disappear if I had rebooted the mashine a few 
>>times. It disappeared if I started a repair from my "repairsystem". 
> 
> 
> What does xfs_db report on the superblock?
> 
>   xfs_db -L /dev/ataraid/d0p1
>   sb 0
>   p
> 
> We had a strange problem where the log region overlapped some other
> filesystem data (see my previous mail) which showed similar
> effects...
> 
> 
> \wlang{}
> 
Ok,
because this thing is not solved (getting filesystem corruption very 
often -especially if rebooting after compiling a lot of stuff on the 
partition...) now another mail with the output of xfs_db....

monster:~ # xfs_db /dev/ataraid/d0p1
xfs_db: sb 0
xfs_db: p
magicnum = 0x58465342
blocksize = 4096
dblocks = 1220932
rblocks = 0
rextents = 0
uuid = 6cac98eb-3e70-4201-b291-15d2f5f2ae8d
logstart = 1048580
rootino = 128
rbmino = 129
rsumino = 130
rextsize = 16
agblocks = 152617
agcount = 8
rbmblocks = 0
logblocks = 1200
versionnum = 0x2084
sectsize = 512
inodesize = 256
inopblock = 16
fname = "\000\000\000\000\000\000\000\000\000\000\000\000"
blocklog = 12
sectlog = 9
inodelog = 8
inopblog = 4
agblklog = 18
rextslog = 0
inprogress = 0
imax_pct = 25
icount = 102912
ifree = 542
fdblocks = 664257
frextents = 0
uquotino = 0
gquotino = 0
qflags = 0
flags = 0
shared_vn = 0
inoalignmt = 2
unit = 0
width = 0
dirblklog = 0
xfs_db:

I hope that this can help to track the problems down.
In Willis mail I read something about an external log, do I really need 
this for my 4Gig root partition if it is even possible on the root 
partition?

Hope you can help me once more ;-)

regards
micha