On Fri, Dec 23, 2011 at 09:37:28AM +, Evan LeCompte wrote:
> I'm having the very same issue as you. I've tried all the latest btrfs tools,
> btrfsck, btrfs-zero-log, restore, find-root etc etc.
>
> All to no avail. only err output is always
>
> "" btrfs_find_last_root: Assertion `!(path->slo
Hi Linus,
My for-linus branch has two commits:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
One is Al's patch in response to my last pull request, but with one small
change to call d_instantiate before trying to log the inode in
btrfs_link.
The other is a double
Hi Chris,
Any updates on the results of another month of full time work on btrfsck?
Thanks,
Erik.
> I've set myself up for disappointment with release dates in the past.
>
> We've found put some really important corruption fixes into the 3.2
> merge window, and the current for-linus branch of
Am 22.12.2011 20:16, schrieb Chris Mason:
On Thu, Dec 22, 2011 at 05:03:19PM +0100, Jan Schmidt wrote:
From: Arne Jansen
This patch adds the possibilty to read-lock an extent even if it is already
write-locked from the same thread. btrfs_find_all_roots() needs this
capability.
I'd rather not
> I've been using btrfs and luks encryption on my Acer netbook for about
> a year now. I haven't had an unmountable corruption on that computer
> yet.
>
> What are your goals now?
I would like to recover the data that is not in the backup.
> Are you trying to recover data from this disk, or are
On Fri, Dec 23, 2011 at 12:12:31AM -0500, Jeff Mahoney wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/21/2011 10:38 PM, Jeff Mahoney wrote:
> > On 12/21/2011 10:21 PM, Liu Bo wrote:
> >> On 12/22/2011 10:59 AM, Jeff Mahoney wrote: Sorry I haven't
> >> responded to this yet. I
On Fri, Dec 23, 2011 at 08:06:03AM -0500, Chris Mason wrote:
> On Fri, Dec 23, 2011 at 01:44:53PM +0300, Dan Carpenter wrote:
> > Hi Josef,
> >
> > Smatch complains about this change introduces a double unlock.
> >
> > fs/btrfs/async-thread.c +608 find_worker(49) error: double unlock
> > 'spin_l
On Fri, Dec 23, 2011 at 01:44:53PM +0300, Dan Carpenter wrote:
> Hi Josef,
>
> Smatch complains about this change introduces a double unlock.
>
> fs/btrfs/async-thread.c +608 find_worker(49) error: double unlock
> 'spin_lock:&workers->lock'
>
>579 spin_unlock_irqres
Hi Josef,
Smatch complains about this change introduces a double unlock.
fs/btrfs/async-thread.c +608 find_worker(49) error: double unlock
'spin_lock:&workers->lock'
579 spin_unlock_irqrestore(&workers->lock, flags);
^^
tgen.org> writes:
>
> So I'm having a bit of trouble with one of my btrfs filesystems. It isn't
mounting after a power failure. I
> can't get restore or btrfsck to run, even on backup supers. I've pasted some
output below. My btrfs-progs
> below come from git this morning, running on linux
10 matches
Mail list logo
