Re: unable to mount a btrfs file system kernel 3.19.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 20 Apr 2015 12:16:33 +0200, Némoz Saint-Dizier, Olivier wrote:

> Hello everyone,
> 
> I have an issue with my ssd where a btrfs partition is located. I have a
> /dev/sdb1 in ext4 for the /boot, and the rest of the ssd is /dev/sdb2
> which is the root of my Archlinux. When I boot, it hangs up after
> loading the kernel. So I tried with an Archlinux liveboot, and I have
> the same behavior with the following trace in logs when I try to mount
> the btrfs partition :

[..snip]

> Apr 11 16:25:56 archiso kernel:  [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
> Apr 11 16:25:56 archiso kernel:  [<ffffffffa043f7ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
> Apr 11 16:25:56 archiso kernel:  [<ffffffffa04c3213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
> Apr 11 16:25:56 archiso kernel:  [<ffffffff8155e999>] schedule+0x29/0x70

> Is it a known bug? Or does someone have an idea about how I could fix
> this issue?

This hang on mount was caused by a backported fix to -stable, which you
probably caught after an update to 3.19.2.

The fix is in 3.19.5: commit 0187ad2b69a51a23924cd41f730e2d923535db80 in
https://kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.19.5

So just get a fresh 3.19.5 (or directly 4.0) and it should mount again.

-h


--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux