> What is your scratch filesystem mount point? Looks like
> this test has a broken output filter (Tim/Ivan?)
>
/.1
:) sorry for this
> Its nothing to worry about by the look of it, broken test.
>
>>
>> I will send .full test dumps to list or anywhere you want. I cant
>> unredstand them myself. But there is no 019.full file.
>>
>
> Just noticed that 019 removes its .full file 3 lines from
> the end of the test - if you comment out that line it'll
> be there at the end - I'd be interested in having a look
> at 019.full.
>
019 - output mismatch (see 019.out.bad)
42,46d41
< File: "./directory/file_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_2"
< Size: 5 Filetype: Regular File
< Mode: (0755/-rwxr-xr-x) Uid: (3) Gid: (1)
< Device: <DEVICE> Inode: <INODE> Links: 1
<
75,79d69
< Device: <DEVICE> Inode: <INODE> Links: 1
<
< File: "./symlink"
< Size: 7 Filetype: Symbolic Link
< Mode: (0123/l--x-w--wx) Uid: (0) Gid: (0)
and 019.full:
*** mkfs ***
meta-data=/dev/sda7 isize=256 agcount=32, agsize=262144
blks
data = bsize=4096 blocks=8279491, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=1200
realtime =none extsz=65536 blocks=0, rtextents=0
*** mount ***
*** umount ***
> cheers.
>
> --
> Nathan
--
Alexey Tsyban
Realtor3D Corp. System Administrator
ICQ 10195188
|