filesystem corruption with 1TB filesystem, 4.9-STABLE, twe

Matthew Seaman m.seaman at infracaninophile.co.uk
Mon Apr 19 08:51:30 PDT 2004


On Mon, Apr 19, 2004 at 03:05:16PM +0100, Ollie Cook wrote:

> I have some further details which I hope might shed some more light on this
> problem. Accessing some files which appear (from a directory listing for
> example) to have been stored correctly results in 'Bad file descriptor'. This
> is with a freshly checked and clean filesystem.
> 
> I say 'clean', but after fsck declares it clean, another pass through fsck will
> diagnose further errors. This is without mounting the filesystem between
> passes.
> 
> I ran a few simple tests and was able to ascertain that the open(2) and read(2)
> system calls don't return errors but fstat(2) does return EBADF.
> 
> su-2.05b# ls | grep 1071701821.78602.aether.uk.clara.net
> 1071701821.78602.aether.uk.clara.net
> su-2.05b# ls  1071701821.78602.aether.uk.clara.net
> ls: 1071701821.78602.aether.uk.clara.net: Bad file descriptor
> 
> Any assistance in diagnosing this would be greatly appreciated.

Can you rule out hardware problems by substituting in a different
known good 3-ware card?  Last time I saw anything like this was an IO
controller chip going marginal through overheating under heavy load
and flipping occasional bits on disk block addresses.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040419/59aefefb/attachment.bin


More information about the freebsd-stable mailing list