Re: [RFC PATCH 2/4 v2] Btrfs: avoid transaction stuff when readonly

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

 



On 12/02/2010 01:41 PM, Mike Fedyk wrote:
> On Wed, Dec 1, 2010 at 8:28 PM, Yan, Zheng <yanzheng@xxxxxxxx> wrote:
>> On Thu, Dec 2, 2010 at 11:42 AM, liubo <liubo2009@xxxxxxxxxxxxxx> wrote:
>>> On 12/01/2010 06:20 PM, liubo wrote:
>>>> When the filesystem is readonly, avoid transaction stuff by checking MS_RDONLY at
>>>> start transaction time.
>>>>
>>> This patch may lead btrfs panic.
>>>
>>> Since btrfs allows transaction under readonly fs state, which is a bit weird, btrfs
>>> does not even check the returned transaction from start_transaction, although it may
>>> return -ENOMEM.
>> btrfs may do log replay even mount as readonly.
>>
> 
> What part is logged besides tree roots and/or superblocks?

log tree is used for log replay after crash and fast fsync and O_SYNC, it logs
inodes.

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

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