Nice patch. However its better if we do this in the btrfs kernel
function btrfs_scan_one_device(). Since the non-canonicalize path
can still sneak through the btrfs specific mount option "device=".
Any comments ?
My initial reaction is to avoid playing naming names within the
kernel. But sinc
Add human readable incompat flags output for btrfs-show-super,
now no longer needs to calculate the hex flags by hand.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add the mising "0x" before hex unknown incompat flags
---
btrfs-show-super.c | 53 +++
While we have a transaction ongoing, the VM might decide at any time
to call btree_inode->i_mapping->a_ops->writepages(), which will start
writeback of dirty pages belonging to btree nodes/leafs. This call
might return an error or the writeback might finish with an error
before we attempt to commit
Original Message
Subject: Re: [PATCH] btrfs: Make btrfs handle security mount options
internally to avoid losing security label.
From: Eric Sandeen
To: Qu Wenruo , Chris Mason ,
Date: 2014年09月24日 11:33
On 9/23/14 7:31 PM, Qu Wenruo wrote:
Original Message --
On 9/23/14 7:31 PM, Qu Wenruo wrote:
>
> Original Message
> Subject: Re: [PATCH] btrfs: Make btrfs handle security mount options
> internally to avoid losing security label.
> From: Eric Sandeen
> To: Chris Mason , Qu Wenruo ,
>
> Date: 2014年09月24日 02:51
>> On 9/23/14 7:49 AM
Add human readable incompat flags output for btrfs-show-super,
now no longer needs to calculate the hex flags by hand.
Signed-off-by: Qu Wenruo
---
btrfs-show-super.c | 53 +
1 file changed, 53 insertions(+)
diff --git a/btrfs-show-super.c b/b
Hello Guys,
I am wondering if anybody here would like to mentor me in the btrfs code base
in if they have
any free time. I am not asking for much just someone to answer my questions and
help me learn
the code base well enough to help out.
Thanks for Any Help,
Nick
--
To unsubscribe from this list
Original Message
Subject: Re: general thoughts and questions + general and RAID5/6 stability?
From: Tobias Holst
To:
Date: 2014年09月23日 22:24
If it is unknown, which of these options have been used at btrfs
creation time - is it possible to check the state of these options
aft
Original Message
Subject: Re: [PATCH] btrfs: Make btrfs handle security mount options
internally to avoid losing security label.
From: Eric Sandeen
To: Chris Mason , Qu Wenruo ,
Date: 2014年09月24日 02:51
On 9/23/14 7:49 AM, Chris Mason wrote:
On 09/23/2014 01:40 AM, Qu Wen
While we have a transaction ongoing, the VM might decide at any time
to call btree_inode->i_mapping->a_ops->writepages(), which will start
writeback of dirty pages belonging to btree nodes/leafs. This call
might return an error or the writeback might finish with an error
before we attempt to commit
While we have a transaction ongoing, the VM might decide at any time
to call btree_inode->i_mapping->a_ops->writepages(), which will start
writeback of dirty pages belonging to btree nodes/leafs. This call
might return an error or the writeback might finish with an error
before we attempt to commit
On 9/23/14 7:49 AM, Chris Mason wrote:
> On 09/23/2014 01:40 AM, Qu Wenruo wrote:
>> [BUG]
>> Originally when mount btrfs with "-o subvol=" mount option, btrfs will
>> lose all security lable.
>> And if the btrfs fs is mounted somewhere else, due to the lost of
>> security lable, SELinux will refus
Hi,
all 5 patches will be in the next integration. I haven't tested them
yet, seems it's a bit more important to make a more stable devel base
for more updates you might want to send.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vg
Damn you gmail...
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Sep 23, 2014 at 10:39 AM, Chris Mason wrote:
>
> This is a starting point for a debugfs style python interface using
> the search ioctl. For now it can only do one thing, which is to
> print out all the extents in a file and calculate the compression ratio.
>
> Over time it will grow more
This is a starting point for a debugfs style python interface using
the search ioctl. For now it can only do one thing, which is to
print out all the extents in a file and calculate the compression ratio.
Over time it will grow more features, especially for the kinds of things
we might run btrfs
Hi,
On Sat, Aug 30, 2014 at 01:00:40PM -0300, Alexandre Oliva wrote:
> Here are the patches.
thanks, I've put them into the queue (branch with other fsck fixes).
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More ma
>> If it is unknown, which of these options have been used at btrfs
>> creation time - is it possible to check the state of these options
>> afterwards on a mounted or unmounted filesystem?
>>
> I don't think there is a specific tool for doing this, but some of them
> do show up in dmesg, for exam
On 2014-09-23 10:23, Tobias Holst wrote:
If it is unknown, which of these options have been used at btrfs
creation time - is it possible to check the state of these options
afterwards on a mounted or unmounted filesystem?
2014-09-23 15:38 GMT+02:00 Austin S Hemmelgarn mailto:ahferro...@gmail.co
On Tue, Sep 23, 2014 at 3:22 PM, Liu Bo wrote:
> This is actually inspired by Filipe's patch. When write_one_eb() fails on
> submit_extent_page(), it'll give up writing this eb and mark it with
> EXTENT_BUFFER_IOERR. So if it's not the last page that encounter the failure,
> there are some left
On Tue, Sep 23, 2014 at 3:05 PM, Liu Bo wrote:
> On Mon, Sep 22, 2014 at 05:41:05PM +0100, Filipe Manana wrote:
>> While we have a transaction ongoing, the VM might decide at any time
>> to call btree_inode->i_mapping->a_ops->writepages(), which will start
>> writeback of dirty pages belonging to
If it is unknown, which of these options have been used at btrfs
creation time - is it possible to check the state of these options
afterwards on a mounted or unmounted filesystem?
2014-09-23 15:38 GMT+02:00 Austin S Hemmelgarn :
>
> Well, running 'mkfs.btrfs -O list-all' with 3.16 btrfs-progs gi
This is actually inspired by Filipe's patch. When write_one_eb() fails on
submit_extent_page(), it'll give up writing this eb and mark it with
EXTENT_BUFFER_IOERR. So if it's not the last page that encounter the failure,
there are some left pages which remain DIRTY, and if a later COW on this eb
On Tue, Sep 23, 2014 at 04:01:41PM +0200, David Sterba wrote:
> On Tue, Sep 23, 2014 at 02:45:44PM +0800, Liu Bo wrote:
> > On Mon, Sep 22, 2014 at 09:57:35PM -0400, nick wrote:
> > > Hello Btfs Developers,
> > > I am new so am unsure of how to fix this but we are hitting some sparse
> > > warning
On Mon, Sep 22, 2014 at 05:41:05PM +0100, Filipe Manana wrote:
> While we have a transaction ongoing, the VM might decide at any time
> to call btree_inode->i_mapping->a_ops->writepages(), which will start
> writeback of dirty pages belonging to btree nodes/leafs. This call
> might return an error
On Tue, Sep 23, 2014 at 02:45:44PM +0800, Liu Bo wrote:
> On Mon, Sep 22, 2014 at 09:57:35PM -0400, nick wrote:
> > Hello Btfs Developers,
> > I am new so am unsure of how to fix this but we are hitting some sparse
> > warnings about unlock/lock is having
> > a wrong count when exiting certain fu
Am 23.09.2014 um 15:38 schrieb Austin S Hemmelgarn:
> On 2014-09-23 09:06, Stefan G. Weichinger wrote:
>> What features for example?
> Well, running 'mkfs.btrfs -O list-all' with 3.16 btrfs-progs gives the
> following list of features:
> mixed-bg- mixed data and metadata block groups
> extr
On Tue, Sep 23, 2014 at 02:03:07PM +0100, Filipe David Manana wrote:
> On Tue, Sep 23, 2014 at 11:14 AM, Liu Bo wrote:
> > On Mon, Sep 22, 2014 at 05:41:04PM +0100, Filipe Manana wrote:
> >> If submit_extent_page() fails in write_one_eb(), we end up with the current
> >> page not marked dirty anym
On 2014-09-23 09:06, Stefan G. Weichinger wrote:
Am 23.09.2014 um 14:08 schrieb Austin S Hemmelgarn:
On 2014-09-22 16:51, Stefan G. Weichinger wrote:
Is re-creating btrfs-filesystems *recommended* in any way?
Does that actually make a difference in the fs-structure?
I would recommend it, the
Am 23.09.2014 um 14:08 schrieb Austin S Hemmelgarn:
> On 2014-09-22 16:51, Stefan G. Weichinger wrote:
>> Is re-creating btrfs-filesystems *recommended* in any way?
>>
>> Does that actually make a difference in the fs-structure?
>>
> I would recommend it, there are some newer features that you can
On Tue, Sep 23, 2014 at 11:14 AM, Liu Bo wrote:
> On Mon, Sep 22, 2014 at 05:41:04PM +0100, Filipe Manana wrote:
>> If submit_extent_page() fails in write_one_eb(), we end up with the current
>> page not marked dirty anymore, unlocked and marked for writeback. But we
>> never
>> end up calling en
Let's say we have a snapshot called "snapshot" on our device "/dev/sdb".
Now we boot a qemu machine and attatch the disk read only (since we do not
want to put our data at risk in the vm, and read only should be enough to
get our snapshot data).
I used
qemu-system-x86_64 -drive -file=/dev/sdb,if=
On Thu, 11 Sep 2014 11:45:34 +0100, Filipe Manana wrote:
> Regression test for btrfs where removing the flag FS_COMPR_FL
> (chattr -c) from an inode wouldn't clear its compression property.
> This was fixed in the following linux kernel patch:
>
> Btrfs: add missing compression property remove
On 09/23/2014 01:40 AM, Qu Wenruo wrote:
> [BUG]
> Originally when mount btrfs with "-o subvol=" mount option, btrfs will
> lose all security lable.
> And if the btrfs fs is mounted somewhere else, due to the lost of
> security lable, SELinux will refuse to mount since the same super block
> is bei
Hi all,
we're testing BTRFS on our Debian server. After a lot of operations
simulating a RAID1 failure, every time I mount my BTRFS RAID1 volume
the kernel logs these messages:
[73894.436173] BTRFS: bdev /dev/etherd/e30.20 errs: wr 33036, rd 0, flush 0,
corrupt 2806, gen 0
[73894.436181] BTRFS:
On 2014-09-22 16:51, Stefan G. Weichinger wrote:
Am 20.09.2014 um 11:32 schrieb Duncan:
What I do as part of my regular backup regime, is every few kernel cycles
I wipe the (first level) backup and do a fresh mkfs.btrfs, activating new
optional features as I believe appropriate. Then I boot to
On Mon, Sep 22, 2014 at 05:41:04PM +0100, Filipe Manana wrote:
> If submit_extent_page() fails in write_one_eb(), we end up with the current
> page not marked dirty anymore, unlocked and marked for writeback. But we never
> end up calling end_page_writeback() against the page, which will make calls
On 23/09/14 07:42, beh...@converseincode.com wrote:
> From: Behan Webster
>
> Replaced the use of a Variable Length Array In Struct (VLAIS) with a C99
> compliant equivalent. This patch allocates the appropriate amount of memory
> using a char array using the SHASH_DESC_ON_STACK macro.
>
> The new
When runing restore under lzo compression, "bad compress length"
problems are encountered.
It is because there is a page align problem with the @decompress_lzo,
as follows:
|--| ||-| |--|...|--|
page ^page page
On Tue, 2014-09-23 at 10:25 +0800, Gui Hecheng wrote:
> When runing restore under lzo compression, "bad compress length"
> problems are encountered.
> It is because there is a page align problem with the @decompress_lzo,
> as follows:
> |--| ||-| |--|...|--|
>
I forgot the attachment. Here it is.
# btrfs-debug-tree -b 13415158087680 /dev/sdh
leaf 13415158087680 items 90 free space 8577 generation 140065 owner 5007
fs uuid 20ccaf09-54ea-486e-9495-9dc91b933e9c
chunk uuid f5a0dea1-b250-4ea4-bf7f-50d30401a708
item 0 key (7516 DIR_INDEX 102) itemoff 1
41 matches
Mail list logo