Tim <t...@tcsac.net> wrote:
> On Sun, Jan 18, 2009 at 8:02 AM, Tom Bird <t...@marmot.org.uk> wrote:
> 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
Using find to search for inodes with st_inode == 0 is not something you may
rely on to work as expected.
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni)
joerg.schill...@fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
