On Wed, Feb 28, 2018 at 05:43:40PM +0100, peteryuchuang@xxxxxxxxx wrote:
> On my laptop, which has just been switched to BTRFS, the root partition
> (a BTRFS partition inside an encrypted LVM. The drive is an NVMe) is
> re-mounted as read-only few minutes after boot.
>
> Trace:
By any chance, are there other messages from btrfs above the line?
>
> [ 199.974591] ------------[ cut here ]------------
> [ 199.974593] BTRFS: Transaction aborted (error -95)
-95 is EOPNOTSUPP, ie operation not supported
> [ 199.974647] WARNING: CPU: 0 PID: 324 at fs/btrfs/inode.c:3042 btrfs_finish_ordered_io+0x7ab/0x850 [btrfs]
btrfs_finish_ordered_io::
3038 btrfs_ordered_update_i_size(inode, 0, ordered_extent);
3039 ret = btrfs_update_inode_fallback(trans, root, inode);
3040 if (ret) {
3041 btrfs_abort_transaction(trans, ret);
3042 goto out;
3043 }
the return code is unexpected here. And seeing 'operation not supported'
after a inode size change looks strange but EOPNOTSUPP could be returned
from some places.
The transaction is aborted from a thread that finalizes some processing
so we don't have enough information here to see how it started. I
suspect there's a file that gets modified short after boot and hits the
problem. I don't think the EOPNOTSUPP is returned from the lower layers
(lvm encryption or nvme), so at this point seems like a btrfs bug.
--
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
