Date: Tue, 04 Jul 2006 09:48:20 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: freebsd-questions@freebsd.org Cc: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Subject: Re: Snapshot problems Message-ID: <44d5clwkez.fsf@be-well.ilk.org> In-Reply-To: <44A987F2.2060906@netfence.it> (Andrea Venturoli's message of "Mon, 03 Jul 2006 23:11:14 %2B0200") References: <44A7A0B8.8050109@netfence.it> <44bqs6n9c2.fsf@be-well.ilk.org> <44A987F2.2060906@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrea Venturoli <ml.diespammer@netfence.it> writes: > Lowell Gilbert wrote: > >>> I believe the first one is a known problem, any more info? >>> >>> Any hint on the second? >> >> Not really; seems strange. >> >> Are you able to fsck the snapshot? > > Hm... guess so. > > Is it "fsck /var/local/snapmnt"? Assuming that is the snapshot file itself, pretty much right. You will need a "-t ffs" in the command as well, and to save time I'd recommend a "-n" also. > Just a question before I try it... this is a production system, will > it screw up anything? No; that's why I suggested fsck'ing the snapshot instead of the real filesystem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44d5clwkez.fsf>