Date: Sun, 11 Jan 2009 20:53:46 -0500 From: "Ben Kaduk" <minimarmot@gmail.com> To: "Xin LI" <delphij@freebsd.org> Cc: svn-src-stable@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, svn-src-stable-7@freebsd.org, freebsd-doc@freebsd.org Subject: Re: svn commit: r187069 - stable/7/sbin/fsck_ffs Message-ID: <47d0403c0901111753r48b9ebc0x43dfb4389194cf2c@mail.gmail.com> In-Reply-To: <200901120039.n0C0dMKX043214@svn.freebsd.org> References: <200901120039.n0C0dMKX043214@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 11, 2009 at 7:39 PM, Xin LI <delphij@freebsd.org> wrote: > Author: delphij > Date: Mon Jan 12 00:39:22 2009 > New Revision: 187069 > URL: http://svn.freebsd.org/changeset/base/187069 > > Log: > MFC revisions 178088 and 179656: Catastrophic recovery mode. > > Modified: > stable/7/sbin/fsck_ffs/ (props changed) > stable/7/sbin/fsck_ffs/fsck.h > stable/7/sbin/fsck_ffs/fsck_ffs.8 > stable/7/sbin/fsck_ffs/fsutil.c > stable/7/sbin/fsck_ffs/inode.c > stable/7/sbin/fsck_ffs/main.c > > Modified: stable/7/sbin/fsck_ffs/fsck.h > ============================================================================== > Modified: stable/7/sbin/fsck_ffs/fsck_ffs.8 > ============================================================================== > --- stable/7/sbin/fsck_ffs/fsck_ffs.8 Sun Jan 11 23:19:17 2009 (r187068) > +++ stable/7/sbin/fsck_ffs/fsck_ffs.8 Mon Jan 12 00:39:22 2009 (r187069) > @@ -29,7 +29,7 @@ > .\" @(#)fsck.8 8.4 (Berkeley) 5/9/95 > .\" $FreeBSD$ > .\" > -.Dd April 24, 2001 > +.Dd April 10, 2008 > .Dt FSCK_FFS 8 > .Os > .Sh NAME > @@ -38,7 +38,7 @@ > .Nd file system consistency check and interactive repair > .Sh SYNOPSIS > .Nm > -.Op Fl BFpfny > +.Op Fl BCFpfny > .Op Fl b Ar block > .Op Fl c Ar level > .Op Fl m Ar mode > @@ -175,6 +175,26 @@ Use the block specified immediately afte > the super block for the file system. > An alternate super block is usually located at block 32 for UFS1, > and block 160 for UFS2. > +.It Fl C > +Run > +.Nm > +in 'catastrophic recovery' mode, which will enable certain aggressive > +operations that can make > +.Nm > +to survive with file systems that has very serious data damage, which > +is an useful last resort when on disk data damage is very serious > +and causes > +.Nm > +to crash otherwise. Be > +.Em very careful > +using this flag, is dangerous if there are data transmission hazards I guess I missed this in HEAD, but there seems to be a missing 'it' before 'is dangerous'. -Ben Kaduk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47d0403c0901111753r48b9ebc0x43dfb4389194cf2c>