Re: btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120

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

 



On Thu, Jul 9, 2015 at 4:52 AM, Vytautas D <vytdau@xxxxxxxxx> wrote:
> <Slightly off topic>
>
> does these bugs exist in systems that converted from ext4 to btrfs using
> kernel 3.13 and then upgraded to kernel 4.1 ?

I don't recall what btrfs-progs and kernel I last tested ext4
conversion with. I know this is a regression, I just don't know how
old it is. I think there's more than one bug here (obviously since
I've filed 4 related bugs in ~24 hours), but I really don't know the
scope of the problem. But the case where the recommended procedure not
only fails but corrupts the file system and it can't be fixed or
rolled back, is not good.

Perhaps the wiki should provide a warning that this is currently
broken, status unknown, or something?

-- 
Chris Murphy
--
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