On Sun, 17 Mar 2013, cwillu <cwi...@cwillu.com> wrote: > On Sat, Mar 16, 2013 at 6:46 AM, Russell Coker <russ...@coker.com.au> wrote: > > On Sat, 16 Mar 2013, cwillu <cwi...@cwillu.com> wrote: > >> On Sat, Mar 16, 2013 at 6:02 AM, Russell Coker <russ...@coker.com.au> wrote: > >> > Is it expected that running btrfsck more than once will keep reporting > >> > errors? > >> > >> Without options, btrfsck does not write to the disk. > > > > The man page for the version in Debian doesn't document any options. > > > > The source indicates that --repair might be the one that's desired, is > > that correct? > > Yes. However, unless something is actually broken, or you've been > advised by a developer, I'd stick with btrfs scrub. > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
I've got a filesystem that causes a kernel panic and can't even get to the scrub stage, so btrfsck is necessary. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703211 While this is an upstream bug, I've filed the above Debian bug report about it. Sometimes in such situations the DD will fix the bug and send the patch upstream. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
