Date: Wed, 12 May 2010 23:23:16 +0200 From: Stefan Bethke <stb@lassitu.de> To: Daniel O'Connor <doconnor@gsoft.com.au> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: .zfs directory broken on an FS Message-ID: <A1C77CD9-1DC2-4D10-BE52-95D741DD6F87@lassitu.de> In-Reply-To: <E9B1B83B-A9C1-448A-9BED-4FE3631DAF8C@gsoft.com.au> References: <E9B1B83B-A9C1-448A-9BED-4FE3631DAF8C@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 12.05.2010 um 02:09 schrieb Daniel O'Connor: > I recently switched over to ZFS at work and it seems pretty good (so = far at least!) however I was writing a script to do snapshots and one of = the file systems now gives.. >=20 > [cain 9:37] ~ >ls -la /usr/local/Genesis/archive/.zfs > ls: snapshot: Bad file descriptor > total 0 >=20 > Other file systems in the same pool work fine though.. > [cain 9:36] ~ >ll /usr/local/Genesis/MeteorData/.zfs/snapshot > total 4 > drwxrwxr-x 32 metdata radar 38 Mar 21 03:11 20100512-0900 >=20 > (All other snapshot directories are OK) This appears to be a long standing issue with no solution. I used to = get this a lot during daily rsync backups; since switching to a zfs = send/recv based script I don't get these problems anymore. Be aware that trying to unmount that snapshot or it's filesystem might = panic or hang the system, including when you try to reboot. Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A1C77CD9-1DC2-4D10-BE52-95D741DD6F87>