On Sun, 2004-04-04 at 12:13, Bailey Kong wrote:
> Hello,
> I was googling around, and I found this thread in the archives
>
> http://oss.sgi.com/projects/xfs/mail_archive/200308/msg00335.html
>
> The suggested fix was:
>
> > That is a corrupt inode on the disk, time to break out xfs_repair. Do
> > a quick mount and unmount of the fs first, then run xfs_check and save
> > the output, finally run xfs_repair and send us the output of both
> > commands.
>
> I was wondering if you guys wanted the outputs from me as well,
>
> I have xfs_check output and xfs_repair -n output as well
>
> http://bailey.tgpsolutions.com/xfs_check
> http://bailey.tgpsolutions.com/xfs_repair
>
> I can also give you guys the output of xfs_repair w/o -n if you wish.
>
> The error seemed to have started Feb 6th, when I was using kernel 2.6.2.
> And is still appearing, even now, when I'm using kernel 2.6.4. My
> version of xfsprogs is 2.6.3.
Just curious was this a 2.4 system that was upgraded to 2.6?
if so was the filesystem clean before the upgrade?
(Not that I'm really expecting you to have checked asking anyways)
Finally did you ever do something directly to the block device while
the fs was mounted? Like run xfs_db?
There is a known problem with accessing a device, even if it's just
read, while the fs is mounted.
>
> Best Regards,
> Bailey
--
Russell Cattelan <cattelan@xxxxxxxxxxx>
-- Attached file included as plaintext by Ecartis --
-- File: signature.asc
-- Desc: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQBAcFZxNRmM+OaGhBgRArLoAJ4jYocwvcYXaIL1RudxPvixb+J4aQCgg4Ce
r+QPKWoA/09nou7h8UdBwVs=
=akRP
-----END PGP SIGNATURE-----
|