On Thu, Feb 07, 2002 at 05:39:32PM -0600, Steve Lord wrote:
> On Thu, 2002-02-07 at 16:49, Alexey Tsyban wrote:
> >
> > Hi,
> >
> > What does this xfs check results mean? File missing? Can I run xfs on this
> > hardware or I need another filesystem?
> >
> > 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)
> >
[very odd, never seen this test fail before]
>
> This test is checking the functionality of a feature of the xfs
> mkfs program to take a filesystem prototype and make a filesystem
> which already has files in it. It is not something that is really
> used on linux (it is used on irix to make root filesystem images).
>
> Possibilities are that it just did not work, or that the user
> space on your system is not compatible with the scripts used
> by the tests to verify the output. How did the rest of the
> tests run?
>
> You could also try running the script by itself rather than through
> the check program and see what output it reports and what it places
> in the filesystem it made.
>
You might also find more useful information to help diagnose
the problem in "019.full".
cheers.
--
Nathan
|