Chris Murphy wrote:
> On Oct 2, 2013, at 10:53 AM, Charles Cazabon wrote:
>
> >> I'd wait until the raid is finished syncing.
> >
> > Strictly speaking, this shouldn't be necessary.
>
> I know but it's a 16TB array, do you really want to start over from scratch?
> No. And neither do most people
On Oct 2, 2013, at 10:53 AM, Charles Cazabon
wrote:
>> I'd wait until the raid is finished syncing.
>
> Strictly speaking, this shouldn't be necessary. mdadm arrays are fully usable
> from creation during the initial sync; the system tracks which bits have been
> initialized and which haven't
Chris Murphy wrote:
> On Oct 1, 2013, at 9:13 PM, Charles Cazabon wrote:
> >
> > Ah, I'm not looking to repair the files -- I can recopy the files easily
> > enough, and rsync will pick up any files whose contents have been corrupted.
>
> If you run a scrub, dmesg should contain the path for aff
On Oct 1, 2013, at 9:13 PM, Charles Cazabon
wrote:
>
> Ah, I'm not looking to repair the files -- I can recopy the files easily
> enough, and rsync will pick up any files whose contents have been corrupted.
> I'd like to get the filesystem fixed, though. i.e., even deleting the
> affected file
Chris Murphy wrote:
> On Oct 1, 2013, at 5:46 PM, Charles Cazabon wrote:
> >
> > # btrfs fi df /media/bigbackup/
> > Data: total=4.53TB, used=4.22TB
> > System, DUP: total=8.00MB, used=508.00KB
> > System: total=4.00MB, used=0.00
> > Metadata, DUP: total=18.00GB, used=17.13GB
> > Metadata:
On Oct 1, 2013, at 5:46 PM, Charles Cazabon
wrote:
>
> # btrfs fi df /media/bigbackup/
> Data: total=4.53TB, used=4.22TB
> System, DUP: total=8.00MB, used=508.00KB
> System: total=4.00MB, used=0.00
> Metadata, DUP: total=18.00GB, used=17.13GB
> Metadata: total=8.00MB, used=0.00
Since the
Hi, Chris,
Chris Murphy wrote:
> On Oct 1, 2013, at 3:12 PM, Charles Cazabon
> wrote:
>
> > Running btrfsck with the --repair option, however, does not appear to fix
> > these [checksum verify] problems. I'll attach the complete output of
> > running with the --repair option; running btrfsck i
On Oct 1, 2013, at 3:12 PM, Charles Cazabon
wrote:
> Greetings,
>
> I've been using btrfs for bulk-storage purposes for a couple of years now (on
> vanilla linux-stable kernels on a few machines). I recently set up a new
> filesystem and have been copying data to it, when I had an unrelated k
Greetings,
I've been using btrfs for bulk-storage purposes for a couple of years now (on
vanilla linux-stable kernels on a few machines). I recently set up a new
filesystem and have been copying data to it, when I had an unrelated kernel
lockup. As expected, after rebooting btrfsck reported some
