Date: Wed, 02 Jul 2014 17:06:39 +0400 From: Alexander Moisseev <moiseev@mezonplus.ru> To: freebsd-stable@freebsd.org Subject: Re: Dump an Unmounted Journaled UFS Filesystem Message-ID: <53B403DF.4080006@mezonplus.ru> In-Reply-To: <20140702175834.3a8c7fa3@X220.alogt.com> References: <CAOD8YqoB%2BZpS9XBgFf2=WjWmsG5f9MsiwSis1cB3irKOOz=ZSw@mail.gmail.com> <CAOD8Yqq5O1ZJ1RwGDTLnLtcvR0MhbLZEfWnOihaJL0xz875pOA@mail.gmail.com> <20140702114213.1396bb21@X220.alogt.com> <53B3A1BB.8070009@mezonplus.ru> <20140702175834.3a8c7fa3@X220.alogt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
02.07.2014 13:58, Erich Dollansky пишет: > Hi, > > On Wed, 02 Jul 2014 10:07:55 +0400 > Alexander Moisseev <moiseev@mezonplus.ru> wrote: > >> 02.07.2014 7:42, Erich Dollansky пишет: >>> what should be wrong by first running a fsck and then the dump? >>> >> >> Erich, what potential problems you expect if the fsck hasn't been ran >> before the dump? >> > I do not know what will be the result if you run a fsck on the restored > file system when it was damaged. > I am sorry, Erich, but I didn't get the point about fsck in given context. OP asked about _unmounted_ journaled filesystem. You can't run fsck write enabled on live file system.But I see no difference between SU and SU+J, if file system is umounted.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53B403DF.4080006>