On Fri, Mar 05, 2004 at 12:53:07PM +1100, Jason White wrote:
> On Thu, 4 Mar 2004, Nathan Scott wrote:
> >
> > Given your kernel version, it sounds alot like theres a kernel
> > bug lurking in there somewhere, we'll need to try to reproduce
> > and address that. Was there anything unusual about that file?
> > (if its still there in lost+found, could you send me the xfs_db
> > dump of that inode?)
>
> To confirm: I can do this with the file system mounted, xfs_db -r
> then inode nnnn (where nnnn is the inode number)
> print
Its not a good idea to do this while mounted in 2.6 atm.
> I will also try to track down whether there was a cron job active around
> the time of the crash that may have moved or deleted the file. I didn't
> notice anything unusual about the file itself - just an ordinary log file
> with entries going back several days. The second inode placed in
> lost+found was empty; for completeness I will send you the dump of that
> too.
OK, thanks.
--
Nathan
|