Tim wrote: > On Sun, Jan 18, 2009 at 8:02 AM, Tom Bird <t...@marmot.org.uk > <mailto:t...@marmot.org.uk>> wrote:
> errors: Permanent errors have been detected in the following files: > > content:<0x0> > content:<0x2c898> > > r...@cs4:~# find /content > /content > r...@cs4:~# (yes that really is it) > Those are supposedly the two inodes that are corrupt. The 0x0 is a bit > scary... you should be able to find out what file(s) they're tied to (if > any) with: > > find /content -inum 0 > find /content -inum 182424 > > If you can live without those files, delete them, export the pool, > re-import, and resilver, and you should be good to go. Hi, well one of the problems is that find doesn't find anything as it is not presenting any files, so I can't delete anything. I've exported the pool but on reimport, I get the same error as I was getting last time something popped: r...@cs4:~# zpool import content cannot open 'content': I/O error Last time, Victor Latushkin fixed it by modifying the file system to point to an older copy of the data. I've not really been following the list of late, any more sign of a fsck.zfs...? thanks -- Tom // www.portfast.co.uk -- internet services and consultancy // hosting from 1.65 per domain _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
