Am Sun, 27 Mar 2016 13:04:25 -0600
schrieb Chris Murphy :
> As for the csum errors with this one single VDI file, you're going to
> have to come up with a way to reproduce it consistently. You'll need
> to have a good copy on a filesystem that comes up clean with btrfs
>
Changing subject to reflect the current topic...
Am Sun, 27 Mar 2016 21:55:40 +0800
schrieb Qu Wenruo :
> > I finally got copy data:
> >
> > # before mounting let's check the FS:
> >
> > $ sudo btrfsck /dev/disk/by-label/usb-backup
> > Checking filesystem on
On Sun, Mar 27, 2016 at 11:31 AM, Kai Krakow wrote:
> Am Sat, 26 Mar 2016 22:57:53 -0600
> schrieb Chris Murphy :
>
>> On Sat, Mar 26, 2016 at 7:30 PM, Kai Krakow
>> wrote:
>>
>> > Both filesystems on this PC show similar
Am Sat, 26 Mar 2016 22:57:53 -0600
schrieb Chris Murphy :
> On Sat, Mar 26, 2016 at 7:30 PM, Kai Krakow
> wrote:
>
> > Both filesystems on this PC show similar corruption now - but they
> > are connected to completely different buses (SATA3 bcache
Am Sun, 27 Mar 2016 14:18:26 +0200
schrieb Martin Steigerwald :
> On Dienstag, 22. März 2016 09:03:42 CEST Kai Krakow wrote:
> > Hello!
> >
> > Since one of the last kernel updates (I don't know which exactly),
> > I'm experiencing csum errors within VDI files when running
>
On 03/27/2016 09:50 AM, Kai Krakow wrote:
Am Sat, 26 Mar 2016 20:30:35 +0100
schrieb Kai Krakow :
Am Wed, 23 Mar 2016 12:16:24 +0800
schrieb Qu Wenruo :
Kai Krakow wrote on 2016/03/22 19:48 +0100:
Am Tue, 22 Mar 2016 16:47:10 +0800
schrieb Qu
On 03/27/2016 03:30 AM, Kai Krakow wrote:
Am Wed, 23 Mar 2016 12:16:24 +0800
schrieb Qu Wenruo :
Kai Krakow wrote on 2016/03/22 19:48 +0100:
Am Tue, 22 Mar 2016 16:47:10 +0800
schrieb Qu Wenruo :
Hi,
Kai Krakow wrote on 2016/03/22 09:03
On Dienstag, 22. März 2016 09:03:42 CEST Kai Krakow wrote:
> Hello!
>
> Since one of the last kernel updates (I don't know which exactly), I'm
> experiencing csum errors within VDI files when running VirtualBox. A
> side effect of this is, as soon as dmesg shows these errors, commands
> like "du"
On Sat, Mar 26, 2016 at 7:30 PM, Kai Krakow wrote:
> Both filesystems on this PC show similar corruption now - but they are
> connected to completely different buses (SATA3 bcache + 3x SATA2
> backing store bache{0,1,2}, and USB3 without bcache = sde), use
> different
On Sat, Mar 26, 2016 at 7:50 PM, Kai Krakow wrote:
>
> # now let's wait for the backup to mount the FS and look at dmesg:
>
> [21375.606479] BTRFS info (device sde1): force zlib compression
> [21375.606483] BTRFS info (device sde1): using free space tree
You're using
Am Sat, 26 Mar 2016 20:30:35 +0100
schrieb Kai Krakow :
> Am Wed, 23 Mar 2016 12:16:24 +0800
> schrieb Qu Wenruo :
>
> > Kai Krakow wrote on 2016/03/22 19:48 +0100:
> > > Am Tue, 22 Mar 2016 16:47:10 +0800
> > > schrieb Qu Wenruo
Am Sat, 26 Mar 2016 15:04:13 -0600
schrieb Chris Murphy :
> On Sat, Mar 26, 2016 at 2:28 PM, Chris Murphy
> wrote:
> > On Sat, Mar 26, 2016 at 1:30 PM, Kai Krakow
> > wrote:
> >> Well, this time it hit me on the USB backup
Am Sat, 26 Mar 2016 14:28:22 -0600
schrieb Chris Murphy :
> On Sat, Mar 26, 2016 at 1:30 PM, Kai Krakow
> wrote:
>
> > Well, this time it hit me on the USB backup drive which uses no
> > bcache and no other fancy options except compress-force=zlib.
On Sat, Mar 26, 2016 at 2:28 PM, Chris Murphy wrote:
> On Sat, Mar 26, 2016 at 1:30 PM, Kai Krakow wrote:
>
>> Well, this time it hit me on the USB backup drive which uses no bcache
>> and no other fancy options except compress-force=zlib.
On Sat, Mar 26, 2016 at 1:30 PM, Kai Krakow wrote:
> Well, this time it hit me on the USB backup drive which uses no bcache
> and no other fancy options except compress-force=zlib. Apparently, I've
> only got a (real) screenshot which I'm going to link here:
>
>
Am Wed, 23 Mar 2016 12:16:24 +0800
schrieb Qu Wenruo :
> Kai Krakow wrote on 2016/03/22 19:48 +0100:
> > Am Tue, 22 Mar 2016 16:47:10 +0800
> > schrieb Qu Wenruo :
> >
> >> Hi,
> >>
> >> Kai Krakow wrote on 2016/03/22 09:03 +0100:
> [...]
>
Kai Krakow wrote on 2016/03/22 19:48 +0100:
Am Tue, 22 Mar 2016 16:47:10 +0800
schrieb Qu Wenruo :
Hi,
Kai Krakow wrote on 2016/03/22 09:03 +0100:
Hello!
Since one of the last kernel updates (I don't know which exactly),
I'm experiencing csum errors within VDI
Am Tue, 22 Mar 2016 21:07:35 +0100
schrieb Henk Slager :
> On Tue, Mar 22, 2016 at 9:03 AM, Kai Krakow
> wrote:
> > Hello!
> >
> > Since one of the last kernel updates (I don't know which exactly),
> > I'm experiencing csum errors within VDI files when
Am Tue, 22 Mar 2016 13:42:00 -0600
schrieb Chris Murphy :
> This is kinda confusing.
Err yes maybe... ;-D
> So the gist is that the guest OS is Windows, so the VDI contains an
> NTFS file system. Correct? And that VDI is on a Btrfs formatted bcache
> device. Correct?
On Tue, Mar 22, 2016 at 9:03 AM, Kai Krakow wrote:
> Hello!
>
> Since one of the last kernel updates (I don't know which exactly), I'm
> experiencing csum errors within VDI files when running VirtualBox. A
> side effect of this is, as soon as dmesg shows these errors,
This is kinda confusing.
So the gist is that the guest OS is Windows, so the VDI contains an
NTFS file system. Correct? And that VDI is on a Btrfs formatted bcache
device. Correct? Does the VDI have +C xattr set?
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe
Am Tue, 22 Mar 2016 16:47:10 +0800
schrieb Qu Wenruo :
> Hi,
>
> Kai Krakow wrote on 2016/03/22 09:03 +0100:
> > Hello!
> >
> > Since one of the last kernel updates (I don't know which exactly),
> > I'm experiencing csum errors within VDI files when running
> >
Am Tue, 22 Mar 2016 09:03:42 +0100
schrieb Kai Krakow :
> Hello!
>
> Since one of the last kernel updates (I don't know which exactly), I'm
> experiencing csum errors within VDI files when running VirtualBox. A
> side effect of this is, as soon as dmesg shows these errors,
Hi,
Kai Krakow wrote on 2016/03/22 09:03 +0100:
Hello!
Since one of the last kernel updates (I don't know which exactly), I'm
experiencing csum errors within VDI files when running VirtualBox. A
side effect of this is, as soon as dmesg shows these errors, commands
like "du" and "df" hang until
Am Tue, 22 Mar 2016 09:03:42 +0100
schrieb Kai Krakow :
> Hello!
>
> Since one of the last kernel updates (I don't know which exactly), I'm
> experiencing csum errors within VDI files when running VirtualBox. A
> side effect of this is, as soon as dmesg shows these errors,
Hello!
Since one of the last kernel updates (I don't know which exactly), I'm
experiencing csum errors within VDI files when running VirtualBox. A
side effect of this is, as soon as dmesg shows these errors, commands
like "du" and "df" hang until reboot.
I've now restored the file from backup
26 matches
Mail list logo