Ok, so you do have V1 dirs... and, you have a fairly recent kernel.
Hm. (Steve did some v1 work a while back, but it should be in your
kernel)
you could also point xfs_repair (-n to do a trial run) and sanity-check
the filesystem.
-Eric
On Mon, 2003-07-21 at 16:54, Josh Fishman wrote:
> On 21 Jul 2003, Eric Sandeen wrote:
>
> > Try xfs_info /mount/point and send the results, this is probably a V1
> > directory filesystem, and V1 is not well supported in Linux.
> >
> > I don't know offhand what the problem might be, but let's see what this
> > fs looks like.
>
> [root@attila /root]# xfs_info /BackupFreeSurfer/mnt/
> meta-data=/BackupFreeSurfer/mnt isize=256 agcount=8, agsize=64675 blks
> data = bsize=4096 blocks=517398, imaxpct=25
> = sunit=0 swidth=0 blks, unwritten=0
> naming =version 1 bsize=4096
> log =internal bsize=4096 blocks=1000 version=1
> = sunit=0 blks
> realtime =none extsz=65536 blocks=0, rtextents=0
>
>
> [root@attila /root]# dmesg
> (...)
> SGI XFS snapshot-xfs-2.4.21-2003-07-07_02:01_UTC with ACLs, realtime, debug
> enabled
> SGI XFS Quota Management subsystem
> XFS mounting filesystem loop(7,0)
> XFS: nil uuid in log - IRIX style log
> Ending clean XFS mount for filesystem: loop(7,0)
>
>
> ... and 'find' is just as powerless as 'ls', though it says "Terminated"
> rather than "out of memory".
>
> Thanks, ---Josh
--
Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc. 651-683-3102
|