Date: Mon, 7 Jan 2008 14:19:47 +0100 From: Jose Garcia Juanino <jjuanino@gmail.com> To: Greg Byshenk <freebsd@byshenk.net> Cc: stable@freebsd.org Subject: Re: Cannot mount a nfs share after doing a snapshot Message-ID: <20080107131947.GA3758@gauss.sanabria.es> In-Reply-To: <20080107110649.GE4601@core.byshenk.net> References: <20080105222831.GA862@gauss.sanabria.es> <20080106144120.GD4601@core.byshenk.net> <20080106163830.GA3790@gauss.sanabria.es> <20080107110649.GE4601@core.byshenk.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--zYM0uCDKw75PZbzx Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El lunes 07 de enero a las 12:06:50 CET, Greg Byshenk escribi=F3: > > # file /.snap/now > > /.snap/now: Unix Fast File system [v2] (little-endian) last mounted on > > /, last written at Sun Jan 6 16:24:19 2008, clean flag 1, readonly flag > > 1, number of blocks 130721, number of data blocks 126520, number of > > cylinder groups 4, block size 16384, fragment size 2048, average file > > size 16384, average number of files in dir 64, pending blocks to free 0, > > pending inodes to free 0, system-wide uuid 0, minimum percentage of free > > blocks 8, TIME optimization >=20 > Ok, so it looks like your /.snap/now snapshot actually exists, and is bei= ng > made, so it looks like the command >=20 > # mount -u -o snapshot /.snap/now / >=20 > is actually working. (So ignore the rest of what I said last time...) >=20 >=20 > I've just played with this a bit myself (I'm no expert, but I use snapsho= ts > currently with 6-STABLE and want to know about any future problems), and I > can reproduce the problem (7.0-PRERELEASE as of 2 Jan 2008). I see the sa= me > sort of errors as you report, and they cannot be cleared even by removing > the snapshot file and restarting nfsd/mountd. The only solution appears to > be to remove the snapshot and restart the machine. I can see how this mig= ht > be a bit inconvenient. >=20 > That said, there appears to be a problem with using the=20 >=20 > # mount -u -o snapshot <snapshot> <filesystem> >=20 > form of the command. >=20 > The problem does _not_ occur (at least in my test) if you use the the >=20 > # mksnap_ffs <filesystem> <snapshot> >=20 > command. Can you try taking a snapshot using mksnap_ffs? Yes, as I have explained in my first post. Taking the snapshot with mksnap_ffs has no problem at all. >=20 > If mksnap_ffs works, while 'mount -u -o' fails, then it looks like a bug.= =2E. > Yes, I think so. The annoying fact is that I am using the sysutils/freebsd-snapshot port to take periodic snapshots and it executes mount -u -o snapshot <snapshot> <filesystem> to make the snapshots instead of mksnap_ffs <filesystem> <snapshot>. Best regards --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHgibzFOo0zaS9RnIRAoZ/AKCgElySmcOWuXFj9yC4Yw9yBJh41wCgqYxm 3mfZlbKFPB5rC0LdiUdkhrg= =iUYC -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080107131947.GA3758>