Re: bad metadata crossing stripe boundary

2016-04-03 Thread Chris Murphy
On Sun, Apr 3, 2016 at 2:51 AM, Marc Haber wrote: > On Sat, Apr 02, 2016 at 01:41:53PM -0600, Chris Murphy wrote: >> > I cryptsetup luksFormat'ted the partition before I mkfs.btrfs'ed it. >> > That should do a much better job than wipefsing it, shouldnt it? >> >> Not

Re: bad metadata crossing stripe boundary

2016-04-03 Thread Marc Haber
On Sat, Apr 02, 2016 at 01:41:53PM -0600, Chris Murphy wrote: > On Thu, Mar 31, 2016 at 11:57 PM, Marc Haber > wrote: > > On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote: > >> Am Thu, 31 Mar 2016 23:00:04 +0200 > >> schrieb Marc Haber

Re: bad metadata crossing stripe boundary

2016-04-03 Thread Marc Haber
On Sat, Apr 02, 2016 at 08:31:17PM +0200, Kai Krakow wrote: > Am Sat, 2 Apr 2016 11:44:32 +0200 > schrieb Marc Haber : > > > On Sat, Apr 02, 2016 at 11:03:53AM +0200, Kai Krakow wrote: > > > Am Fri, 1 Apr 2016 07:57:25 +0200 > > > schrieb Marc Haber

Re: bad metadata crossing stripe boundary

2016-04-02 Thread Chris Murphy
On Thu, Mar 31, 2016 at 11:57 PM, Marc Haber wrote: > On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote: >> Am Thu, 31 Mar 2016 23:00:04 +0200 >> schrieb Marc Haber : >> > I find it somewhere between funny and disturbing that the

Re: bad metadata crossing stripe boundary

2016-04-02 Thread Patrik Lundquist
On 2 April 2016 at 20:31, Kai Krakow wrote: > Am Sat, 2 Apr 2016 11:44:32 +0200 > schrieb Marc Haber : > >> On Sat, Apr 02, 2016 at 11:03:53AM +0200, Kai Krakow wrote: >> > Am Fri, 1 Apr 2016 07:57:25 +0200 >> > schrieb Marc Haber

Re: bad metadata crossing stripe boundary

2016-04-02 Thread Kai Krakow
Am Sat, 2 Apr 2016 11:44:32 +0200 schrieb Marc Haber : > On Sat, Apr 02, 2016 at 11:03:53AM +0200, Kai Krakow wrote: > > Am Fri, 1 Apr 2016 07:57:25 +0200 > > schrieb Marc Haber : > > > On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai

Re: bad metadata crossing stripe boundary

2016-04-02 Thread Marc Haber
On Sat, Apr 02, 2016 at 11:03:53AM +0200, Kai Krakow wrote: > Am Fri, 1 Apr 2016 07:57:25 +0200 > schrieb Marc Haber : > > On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote: > > > Am Thu, 31 Mar 2016 23:00:04 +0200 > > > schrieb Marc Haber

Re: bad metadata crossing stripe boundary

2016-04-02 Thread Kai Krakow
Am Fri, 1 Apr 2016 07:57:25 +0200 schrieb Marc Haber : > On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote: > > Am Thu, 31 Mar 2016 23:00:04 +0200 > > schrieb Marc Haber : > > > I find it somewhere between funny and disturbing

Re: bad metadata crossing stripe boundary

2016-03-31 Thread Marc Haber
On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote: > Am Thu, 31 Mar 2016 23:00:04 +0200 > schrieb Marc Haber : > > I find it somewhere between funny and disturbing that the first call > > of btrfs check made my kernel log the following: > > Mar 31 22:45:36 fan

Re: bad metadata crossing stripe boundary

2016-03-31 Thread Kai Krakow
ry the following patch based on v4.5 > > > btrfs-progs? https://patchwork.kernel.org/patch/8706891/ > > > > This also fixes the "bad metadata crossing stripe boundary" on my > > pet patient. > > > > I find it somewhere between funny and disturbin

Re: bad metadata crossing stripe boundary

2016-03-31 Thread Kai Krakow
t; This also fixes the "bad metadata crossing stripe boundary" on my pet > patient. > > I find it somewhere between funny and disturbing that the first call > of btrfs check made my kernel log the following: > Mar 31 22:45:36 fan kernel: [ 6253.178264] EXT4-fs (dm-31): moun

Re: bad metadata crossing stripe boundary

2016-03-31 Thread Marc Haber
On Thu, Mar 31, 2016 at 10:31:49AM +0800, Qu Wenruo wrote: > Would you please try the following patch based on v4.5 btrfs-progs? > https://patchwork.kernel.org/patch/8706891/ This also fixes the "bad metadata crossing stripe boundary" on my pet patient. I find it somewhe

Re: bad metadata crossing stripe boundary

2016-03-31 Thread Henk Slager
>> Would you please try the following patch based on v4.5 btrfs-progs? >> https://patchwork.kernel.org/patch/8706891/ >> >> According to your output, all the output is false alert. >> All the extent starting bytenr can be divided by 64K, and I think at >> initial time, its 'max_size' may be set to

Re: bad metadata crossing stripe boundary

2016-03-31 Thread Kai Krakow
Am Thu, 31 Mar 2016 10:31:49 +0800 schrieb Qu Wenruo : > Qu Wenruo wrote on 2016/03/31 09:33 +0800: > > > > > > Kai Krakow wrote on 2016/03/28 12:02 +0200: > >> Changing subject to reflect the current topic... > >> > >> Am Sun, 27 Mar 2016 21:55:40 +0800 > >> schrieb Qu

Re: bad metadata crossing stripe boundary

2016-03-30 Thread Qu Wenruo
Qu Wenruo wrote on 2016/03/31 09:33 +0800: Kai Krakow wrote on 2016/03/28 12:02 +0200: 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

Re: bad metadata crossing stripe boundary

2016-03-30 Thread Qu Wenruo
Kai Krakow wrote on 2016/03/28 12:02 +0200: 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

bad metadata crossing stripe boundary (was: csum errors in VirtualBox VDI files)

2016-03-28 Thread Kai Krakow
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