Date: Wed, 26 Jun 2019 05:55:08 +0000 From: "Thomas Mueller" <mueller6722@twc.com> To: freebsd-questions@freebsd.org Subject: Re: Can I recreate my .snap directories ? References: <2214.1561413756@segfault.tristatelogic.com> <CAHu1Y702UxMiFURL56-CrLUz%2B4SEPLirsYZXBz1B8=_x6rWUKw@mail.gmail.com> <20190625004825.AF1CB71804F@kicp.uchicago.edu> <2fd51656-05c5-c609-a355-7275aab9cbb7@kicp.uchicago.edu> <201906260411.x5Q4BBiG001918@r56.edvax.de> <20190626063657.d31006a6.freebsd@edvax.de>
| previous in thread | raw e-mail | index | archive | help
from Polytropon:
> On Tue, 25 Jun 2019 19:25:21 +0000, Thomas Mueller wrote:
> > UFS-1 or 2 file system created by NetBSD would not have .snap directory.
> FreeBSD's newfs supports the following option:
> -n Do not create a .snap directory on the new file system. The
> resulting file system will not support snapshot generation, so
> dump(8) in live mode and background fsck(8) will not function
> properly. The traditional fsck(8) and offline dump(8) will work
> on the file system. This option is intended primarily for memory
> or vnode-backed file systems that do not require dump(8) or
> fsck(8) support.
> This limits the use of dump and fsck, but if you're not using those
> specific features, .snap won't be needed.
NetBSD fsck_ffs works on UFS-1 or 2 file system, lack of .snap directory is no impediment.
I have rescued FreeBSD file systems by booting into NetBSD and running their fsck_ffs when fsck_ffs from FreeBSD was not good enough.
Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>