On Tue, 14 Feb 2012, Timo Nentwig wrote:
Date: Tue, 14 Feb 2012 18:37:16 +0100 (CET)
From: Timo Nentwig
To: linux-btrfs@vger.kernel.org
Subject: Re: can't read superblock (but could mount)
On Mon, 13 Feb 2012, Chris Mason wrote:
btrfs-debug-tree -b 9872289792 /dev/xxx
Hm, just d
On Thu, Feb 16, 2012 at 06:04:47PM +0100, Timo Nentwig wrote:
>
>
> On Wed, 15 Feb 2012, Chris Mason wrote:
>
> >Date: Wed, 15 Feb 2012 08:23:22 -0500
> >From: Chris Mason
> >To: Timo Nentwig
> >Cc: linux-btrfs@vger.kernel.org
> >Subject: Re: can
On Wed, 15 Feb 2012, Chris Mason wrote:
Date: Wed, 15 Feb 2012 08:23:22 -0500
From: Chris Mason
To: Timo Nentwig
Cc: linux-btrfs@vger.kernel.org
Subject: Re: can't read superblock (but could mount)
On Wed, Feb 15, 2012 at 07:03:49AM +0100, Timo Nentwig wrote:
On Tue, 14 Feb 2012,
On Wed, Feb 15, 2012 at 07:03:49AM +0100, Timo Nentwig wrote:
>
>
> On Tue, 14 Feb 2012, Chris Mason wrote:
>
> >Ok, 3.2 shouldn't have done this. Was this an external drive? What
> >else do you have on the system?
>
> Nothing special actually. Standard arch linux with virtualbox kernel modul
On Tue, 14 Feb 2012, Chris Mason wrote:
Ok, 3.2 shouldn't have done this. Was this an external drive? What
else do you have on the system?
Nothing special actually. Standard arch linux with virtualbox kernel modules.
It's a SSD if this should matter. Mounted with ssd,compress=lzo,noatime.
On Tue, Feb 14, 2012 at 07:54:43PM +0100, Timo Nentwig wrote:
>
>
> On Tue, 14 Feb 2012, Chris Mason wrote:
>
> >As for how we got here, I think you said you were originally running
> >something older than 3.2 when these problems started, correct?
>
> Nope, I was already on 3.2.1 or 3.2.4. I re
On Tue, 14 Feb 2012, Chris Mason wrote:
As for how we got here, I think you said you were originally running
something older than 3.2 when these problems started, correct?
Nope, I was already on 3.2.1 or 3.2.4. I restored a backup in the meantime
and already had to soft-reset the box:
# ls
On Tue, Feb 14, 2012 at 06:37:16PM +0100, Timo Nentwig wrote:
> On Mon, 13 Feb 2012, Chris Mason wrote:
>
> >btrfs-debug-tree -b 9872289792 /dev/xxx
>
> # btrfs-debug-tree -b 9872289792 /dev/loop1
> leaf 9872289792 items 51 free space 0 generation 120351 owner 5
Ok, so this block is full of dire
On Mon, 13 Feb 2012, Chris Mason wrote:
btrfs-debug-tree -b 9872289792 /dev/xxx
# btrfs-debug-tree -b 9872289792 /dev/loop1
leaf 9872289792 items 51 free space 0 generation 120351 owner 5
fs uuid 9e9886fc-3e60-4c59-a246-727662769ee2
chunk uuid f7e4ac1e-f4d6-436b-9bda-8409311dcdb6
item
On Sat, Feb 11, 2012 at 07:27:25AM +0100, bt...@nentwig.biz wrote:
>
> Quoting Chris Mason :
>
> >On Fri, Feb 10, 2012 at 05:18:42PM -0500, Chris Mason wrote:
> >>Ok, step one:
> >>
> >>Pull down the dangerdonteveruse branch of btrfs-progs:
> >>
> >>git://git.kernel.org/pub/scm/linux/kernel/git/m
Quoting Chris Mason :
On Fri, Feb 10, 2012 at 05:18:42PM -0500, Chris Mason wrote:
Ok, step one:
Pull down the dangerdonteveruse branch of btrfs-progs:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
dangerdonteveruse
Run btrfs-debug-tree -r /dev/sda1 and send the out
On Fri, Feb 10, 2012 at 05:18:42PM -0500, Chris Mason wrote:
> On Fri, Feb 10, 2012 at 08:30:51PM +0100, bt...@nentwig.biz wrote:
> > Hi!
> >
> > I used to have arch linux running on 1 btrfs partition (sda1, incl. /boot).
> > When switching to 3.2.5 recently the system fails to boot:
> >
> > (aft
On Fri, Feb 10, 2012 at 08:30:51PM +0100, bt...@nentwig.biz wrote:
> Hi!
>
> I used to have arch linux running on 1 btrfs partition (sda1, incl. /boot).
> When switching to 3.2.5 recently the system fails to boot:
>
> (after udevd)
> /etc/rc.sysinit: line 15: 117 Bus error mountpoint -q /proc
>
Hi!
I used to have arch linux running on 1 btrfs partition (sda1, incl. /boot).
When switching to 3.2.5 recently the system fails to boot:
(after udevd)
/etc/rc.sysinit: line 15: 117 Bus error mountpoint -q /proc
and so on, no idea.
It used to boot with 3.2.4, but
1) I obviously had some corr
14 matches
Mail list logo