Date: Thu, 13 Nov 2014 23:21:10 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: javocado <javocado@gmail.com> Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: ZFS + xattr -> panic loop Message-ID: <54653CE6.2090301@multiplay.co.uk> In-Reply-To: <CAP1HOmTp9V6ycg%2BZcY_mhRRsPLUTDM2_y5TWpJ3cm1K-Kw6_sQ@mail.gmail.com> References: <CAP1HOmTNcSrJzw6H777iJvcKG%2BeCv5L%2Bt0jcR7ccYX5eRXxhGg@mail.gmail.com> <5465129C.7020606@multiplay.co.uk> <CAP1HOmTp9V6ycg%2BZcY_mhRRsPLUTDM2_y5TWpJ3cm1K-Kw6_sQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I've recommend moving to 10.1 and seeing if your still see the same issue. If your zpool is corrupt and this can't recover from it you may need to restore from a backup. On 13/11/2014 23:18, javocado wrote: > Apologies: > > FreeBSD hostname 8.3-RELEASE FreeBSD 8.3-RELEASE #1: Wed Sep 18 > 16:59:03 MDT 2013 amd64 > > On Thu, Nov 13, 2014 at 12:20 PM, Steven Hartland > <killing@multiplay.co.uk <mailto:killing@multiplay.co.uk>> wrote: > > Alwas good to include which version of the OS your talking about > (uname -a) > > > On 13/11/2014 19:43, javocado wrote: > > After running an rsync (upload) into my zfs filesystem using the > --fake-super option (which stores permissions in extended > attributes) the > zfs filesystem has somehow become corrupt. When booting the > system it > panic's upon zfs startup: > > panic: solaris assert: VFS_ROOT(vfsp, LK_EXCLUSIVE, &vp) == 0, > file: > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vfsops.c > , line: 1170 > cpuid = 12 > KDB: stack backtrace: > #0 0xffffffff8034b3ae at kdb_backtrace+0x5e > #1 0xffffffff803185c7 at panic+0x187 > #2 0xffffffff80ab8213 at zfs_mount+0x563 > #3 0xffffffff803a2635 at vfs_donmount+0xdc5 > #4 0xffffffff803a3133 at nmount+0x63 > #5 0xffffffff80553284 at amd64_syscall+0x1f4 > #6 0xffffffff8053bc2c at Xfast_syscall+0xfc > > I was able to boot the system by setting the filesystem: > > canmount=off > > However, I am still unable to mount it manually without > causing a similar > panic. > > So, setting the cause of the panic aside for the moment, I > just want to get > to the data. I'd like to think I can do that by turning off > xattrs and > mounting it read-only however: > > # zfs set xattr=off pool/data > property 'xattr' not supported on FreeBSD: permission denied > > How can I turn that off? > > Second or alternately, if I want to just dump the filesystem > out excluding > the extended attributes, so that I have a clean, mountable > data set, how > would I do that? > > Thank you! > _______________________________________________ > freebsd-fs@freebsd.org <mailto:freebsd-fs@freebsd.org> mailing > list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to > "freebsd-fs-unsubscribe@freebsd.org > <mailto:freebsd-fs-unsubscribe@freebsd.org>" > > > _______________________________________________ > freebsd-fs@freebsd.org <mailto:freebsd-fs@freebsd.org> mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to > "freebsd-fs-unsubscribe@freebsd.org > <mailto:freebsd-fs-unsubscribe@freebsd.org>" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54653CE6.2090301>