Hi,
a collection of fixes (lockdep, delayed ref locking, dio). The
btrfs_uuid_tree_iterate return value fix has a visible impact so it's added to
the mix. Please pull.
The following changes since commit 2939e1a86f758b55cdba73e29397dd3d94df13bc:
btrfs: limit async_work allocation and worker
On 2017-01-04 17:12, Janos Toth F. wrote:
I separated these 9 camera storages into 9 subvolumes (so now I have
10 subvols in total in this filesystem with the "root" subvol). It's
obviously way too early to talk about long term performance but now I
can tell that recursive defrag does NOT
On Wed, Jan 04, 2017 at 03:52:47PM +0800, Qu Wenruo wrote:
> Any comment on this patch?
>
> Without it, btrfs will always fail for generic/387.
The fix looks good to me, adding it to next. There's a very similar
pattern in btrfs_punch_hole, but this function uses the trans reserve
and not
Hi all,
The CFP for the Linux Foundation's Vault conference is coming close to an end.
The event is being held this year in Cambridge, Massachusetts on the days
following the LSF/MM summit.
The first two year's events have been solid, focused events in my (slightly
biased) opinion, so worth
Signed-off-by: Lakshmipathi.G
---
btrfs-corrupt-block.c | 48
1 file changed, 48 insertions(+)
diff --git a/btrfs-corrupt-block.c b/btrfs-corrupt-block.c
index a2f35ab..0e1eb52 100644
--- a/btrfs-corrupt-block.c
+++
Signed-off-by: Lakshmipathi.G
---
tests/fsck-tests/027-missing-data-csum/test.sh | 39 ++
1 file changed, 39 insertions(+)
create mode 100755 tests/fsck-tests/027-missing-data-csum/test.sh
diff --git
Duncan posted on Thu, 05 Jan 2017 09:23:35 + as excerpted:
> In his case the copying was from 7.2krpm to 5.6krpm drives, but not the
> reverse or when copying from slower to faster.
Ugh. What I /meant/ was:
Slower to faster: worked
Between same speeds:worked
Faster to slower:
From: Robbie Ko
Under certain situations, an incremental send operation can
a rmdir operation that will make the receiving end fail when
attempting to execute it, because the path is not exist.
Example scenario:
Parent snapshot:
| d259_old/ (ino 259, gen 96)
From: Robbie Ko
Under certain situations, an incremental send operation can
a rename operation that will make the receiving end fail when
attempting to execute it, because the source has been deleted.
Example scenario:
Parent snapshot:
| d1/ (ino 257, gen
From: Robbie Ko
Under certain situations, an incremental send operation can
delay rmdir operation when processing inode 258, but it is
not necessary, because dir258 is empty.
Example scenario:
Parent snapshot:
| dir258/ (ino 258, gen 27)
| dir257/ (ino 257,
From: Robbie Ko
Under certain situations, an incremental send operation can
a utime operation that will make the receiving end fail when
attempting to execute it, because the path has been deleted.
Exampla scenario:
Parent snapshot:
| dir258/ (ino 258, gen 7,
Matt McKinnon posted on Wed, 04 Jan 2017 10:25:17 -0500 as excerpted:
> Hi All,
>
> I seem to have a similar issue to a subject in December:
>
> Subject: page allocation stall in kernel 4.9 when copying files from one
> btrfs hdd to another
>
> In my case, this is caused when rsync'ing large
From: Robbie Ko
Patch for fix btrfs incremental send.
These patches base on v4.8.0-rc8
V3: Improve the change log
V2: Add a new patch "add generation check in existence demtermination for
the parent directory"
Robbie Ko (6):
Btrfs: incremental send, fix failure to
From: Robbie Ko
Under certain situations, an incremental send operation can
a rename operation that will make the receiving end fail when
attempting to execute it, because the target is exist.
Example scenario:
Parent snapshot:
|.(ino 256, gen 5)
| a1/
From: Robbie Ko
Under certain situations, an incremental send operation can
a truncate operation that will make the receiving end fail when
attempting to execute it, because the path is not exist.
Example scenario:
Parent snapshot:
| dir258/ (ino 258, gen 15, dir)
On Thu, Jan 5, 2017 at 5:22 AM, robbieko wrote:
> Filipe Manana 於 2017-01-04 21:07 寫到:
>
>> On Wed, Jan 4, 2017 at 10:53 AM, robbieko wrote:
>>>
>>> From: Robbie Ko
>>>
>>> Test that an incremental send operation dosen't work
Hi.
This looks bit like at my issue with the differential sending/receiving
and snapshot deleting.
Thanks for the test cases and for the patches.
Regards.
Gdb
>>robbieko Thu, 05 Jan 2017 00:47:54 -0800
>>From: Robbie Ko
>>Patch for fix btrfs incremental send.
Patch with fix for David Sterba review comment.
Signed-off-by: Lakshmipathi.G
---
btrfs-corrupt-block.c | 8
1 file changed, 8 insertions(+)
diff --git a/btrfs-corrupt-block.c b/btrfs-corrupt-block.c
index 16680df..a2f35ab 100644
--- a/btrfs-corrupt-block.c
On Thu, Jan 5, 2017 at 2:45 AM, robbieko wrote:
> Filipe Manana 於 2017-01-04 21:09 寫到:
>
>> On Wed, Jan 4, 2017 at 10:53 AM, robbieko wrote:
>>>
>>> From: Robbie Ko
>>>
>>> Test that an incremental send operation dosen't' work
Hi all,
I'm running Fedora 25 with kernel 4.8.15 (also tested 4.8.14), and when
I go to mount my USB BTRFS filesystem, the PC freezes completely.
I have managed to get a kernel crash once out of the number of freezes -
and I have attached that log. I have also posted a copy here:
On 01/05/2017 10:22 AM, David Sterba wrote:
Hi,
a collection of fixes (lockdep, delayed ref locking, dio). The
btrfs_uuid_tree_iterate return value fix has a visible impact so it's added to
the mix. Please pull.
The following changes since commit 2939e1a86f758b55cdba73e29397dd3d94df13bc:
Hello,
I just got a BUG on mount of a raid10 fs. /dev/sde was added to
the fs recently and balance has been started. After reboot (balance
still running), the fs can not be mounted any more.
# btrfs fi sh
Label: 'BTR0' uuid: 0ec83db3-4574-4e40-8d57-ebbe9fe246e1
Total devices 5 FS
Signed-off-by: Nicholas D Steeves
---
Documentation/btrfs-device.asciidoc | 2 +-
Documentation/btrfs-quota.asciidoc | 4 ++--
image/main.c| 2 +-
mkfs/main.c | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git
Hi,
This is just another trivial patch for typos/spelling in user facing strings.
Sincerely,
Nicholas
Nicholas D Steeves (1):
Fix spelling/typos in user-facing strings.
Documentation/btrfs-device.asciidoc | 2 +-
Documentation/btrfs-quota.asciidoc | 4 ++--
image/main.c
Since a zero-length dedupe operation is guaranteed to succeed, use that
to test whether or not this filesystem supports dedupe.
Signed-off-by: Darrick J. Wong
---
v2: declare variables on the stack instead of introducing fake types
---
file_scan.c | 45
25 matches
Mail list logo