Thanks Dave, I was finally approved, but with "Nazar Mokrynskyi2" username)
Any chance to update username to Nazar Mokrynskyi (without "2" at the end)?
I've already changed Real name.
Tried to reply on admin's email, but it doesn't accept emails actually,
so I have to ask here again.
Sincerely
On Sat, Aug 29, 2015 at 9:23 PM, Kenneth Lakin wrote:
> Hey. It looks like I'm being bitten by:
> http://article.gmane.org/gmane.comp.file-systems.btrfs/44987/ except I'm
> hitting it during rename, rather than unlink. Dmesg spew here:
> http://pastebin.ca/3137198 (That pastebin post includes the
On 05/01/12 11:09, Daniel Pocock wrote:
>
>>
>> From there on, one could potentially create a matrix: (proportional
>> font art, apologies):
>>
>> | subvol1 | subvol2 | subvol3 |
>> --+--+--+--+
>> subvol1 | 200M | 20M | 50M |
>> -
When creating small Btrfs filesystem instances (i.e. filesystem size <= 1GiB),
mkfs.btrfs can fail if "data block size" does not match "metadata block
size". In such cases this commit aborts the test instead of letting it to
continue and report misleading results.
Signed-off-by: Chandan Rajendra
For small filesystem instances (i.e. size <= 1 GiB), mkfs.btrfs fails when
"data block size" does not match with the "metadata block size" specified on
the mkfs.btrfs command line. This commit increases the size of filesystem
instance created so that the test can be executed on subpagesize-blocksiz
Does anyone know when this changed? Maybe it's a 4.2 thing... anyway
it's very much welcome!
/dev/sda2 on /home type btrfs
(rw,relatime,seclabel,space_cache,subvolid=258,subvol=/home)
/dev/sdc1 on /brick0 type btrfs
(rw,relatime,seclabel,space_cache,subvolid=5,subvol=/)
/dev/sde on /brick1 type
Improve readability by generalizing the profile validity checks,
I had to read through those if statements half a dozen times on my
first try just to get an idea of what's happening there.
Signed-off-by: Alexandru Moise <00moses.alexande...@gmail.com>
---
fs/btrfs/volumes.c | 21 -
On Sun, Aug 30, 2015 at 08:14:48PM +0530, Chandan Rajendra wrote:
> When creating small Btrfs filesystem instances (i.e. filesystem size <= 1GiB),
> mkfs.btrfs can fail if "data block size" does not match "metadata block
> size". In such cases this commit aborts the test instead of letting it to
>
David Sterba wrote on 2015/08/27 11:14 +0200:
On Mon, Aug 03, 2015 at 03:18:55PM +0800, Qu Wenruo wrote:
Implement details includes the following:
1) LRU hash maps to limit the memory usage
The hash -> extent mapping is control by LRU (or unlimited), to
get a controllable memory usag
Alexandru Moise wrote on 2015/08/29 11:45 +:
This patch reverts commit: b4fcd6be6bbd702ae1a6545c9b413681850a9814
Wang Shilong added those casts as a workaround for a bug reproduced
using the following steps:
Steps to reproduce:
mkfs.btrfs
mount
dd if=/dev/zero o
Hi, David Sterba
> -Original Message-
> From: David Sterba [mailto:dste...@suse.cz]
> Sent: Saturday, August 29, 2015 1:24 AM
> To: Zhao Lei
> Cc: linux-btrfs@vger.kernel.org
> Subject: Re: [PATCH 0/4] btrfs-progs: Use common function to parse unit
> arguments
>
> On Thu, Aug 27, 2015 at
Daniel Pocock wrote on 2015/08/30 14:31 +0200:
On 05/01/12 11:09, Daniel Pocock wrote:
From there on, one could potentially create a matrix: (proportional
font art, apologies):
| subvol1 | subvol2 | subvol3 |
--+--+--+--+
subvol1 | 200M
If a testcase failed, we can't run it(or other tests needs mount) again,
# ./misc-tests.sh 007
[TEST] 007-subvolume-sync
failed: fail
test failed for case 007-subvolume-sync
# ./misc-tests.sh 007
[TEST] 007-subvolume-sync
failed: mount /root/btrfs-progs/tests/test.img /root/b
If a testcase failed, we can't run it(or other tests needs mount) again,
# ./misc-tests.sh 007
[TEST] 007-subvolume-sync
failed: fail
test failed for case 007-subvolume-sync
# ./misc-tests.sh 007
[TEST] 007-subvolume-sync
failed: mount /root/btrfs-progs/tests/test.img /root/b
So this test can support both block device and loop device simply.
Signed-off-by: Zhao Lei
---
tests/misc-tests/007-subvolume-sync/test.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/misc-tests/007-subvolume-sync/test.sh
b/tests/misc-tests/007-subvolume-sync/te
When using loop device for test, fsck-tests/013-extent-tree-rebuild
failed with following error message:
# ./fsck-tests.sh
...
[TEST] 013-extent-tree-rebuild
failed: mount /data/btrfsprogs/tests/test.img /data/btrfsprogs/tests/mnt
test failed for case 013-extent-tree-rebuild
#
Cons
For example, $TEST_DIR is common used in severial tests, and have
duplicated code for initialize.
These duplicated code not only benifits harddisk vendor, but have
inconsistent details, as:
convert-tests.sh: lack of mkdir
fsck-tests/012-leaf-corruption/test.sh: unnecessary mkdir
fsck-tests/0
On Tue, Aug 25, 2015 at 12:39:26PM +0800, Anand Jain wrote:
> From: Anand Jain
>
> Controlled EIO from the device is achieved using the dm device.
> Helper functions are at common/dmerror.
>
> Broadly steps will include calling _dmerror_init().
> _dmerror_init() will use SCRATCH_DEV to create dm
On Sun, Aug 30, 2015 at 11:17:44AM -0600, Chris Murphy wrote:
> Does anyone know when this changed? Maybe it's a 4.2 thing... anyway
> it's very much welcome!
>
> /dev/sda2 on /home type btrfs
> (rw,relatime,seclabel,space_cache,subvolid=258,subvol=/home)
>
> /dev/sdc1 on /brick0 type btrfs
> (rw
On Mon, Aug 31, 2015 at 09:44:49AM +0800, Qu Wenruo wrote:
> >>>From the perspective of users, qgroup's referenced or exclusive
> >>is negative,but user can not continue to write data! a workaround
> >>way is to cast u64 to s64 when doing qgroup reservation
> >
> >I am unable to reprodu
Alexandru Moise wrote on 2015/08/31 09:32 +0300:
On Mon, Aug 31, 2015 at 09:44:49AM +0800, Qu Wenruo wrote:
>From the perspective of users, qgroup's referenced or exclusive
is negative,but user can not continue to write data! a workaround
way is to cast u64 to s64 when doing qgroup
On Mon, Aug 31, 2015 at 02:51:08PM +0800, Qu Wenruo wrote:
>
>
> Alexandru Moise wrote on 2015/08/31 09:32 +0300:
> >On Mon, Aug 31, 2015 at 09:44:49AM +0800, Qu Wenruo wrote:
> >From the perspective of users, qgroup's referenced or exclusive
> is negative,but user can not continu
22 matches
Mail list logo
