Am Freitag, 20. März 2015, 12:59:14 schrieb Filipe David Manana:
On Fri, Mar 20, 2015 at 12:39 PM, David Sterba dste...@suse.cz wrote:
On Thu, Mar 19, 2015 at 09:47:15PM +, Filipe David Manana wrote:
On Thu, Mar 19, 2015 at 1:21 PM, David Sterba dste...@suse.cz
wrote:
On Wed, Mar 18,
From: Zhao Lei zhao...@cn.fujitsu.com
btrfs will report no_space when we run following write and delete
file loop:
# FILE_SIZE_M=[ 75% of fs space ]
# DEV=[ some dev ]
# MNT=[ some dir ]
#
# mkfs.btrfs -f $DEV
# mount -o nodatacow $DEV $MNT
# for ((i = 0; i 100; i++)); do dd if=/dev/zero
From: Zhao Lei zhao...@cn.fujitsu.com
This is another fix of no_space case.
All patchs for fix no_space bug are available at fix_no_space
branch on:
git://github.com/zhaoleidd/btrfs
Any suggestions are welcome.
Zhao Lei (1):
btrfs: wait for delayed iputs on no space
Hello All,
I am a CS graduate student from Carnegie Mellon University. I am
hoping to build the feature - Content based storage mode under
Google Summer of Code 2015. This project has also been listed as an
idea on BTRFS ideas page. However, I have not found a mentor yet, and
without a mentor I
On Thu, Mar 26, 2015 at 07:45:07PM -0400, nick wrote:
I have a patch for moving over the rcu-string header file for btrfs to
the standard include headers in include/linux
as you stated this on a to do on the brtfs to do page for the
project's wiki page.
The wiki page states that the task is
Even though we delay the rename of directories when they become
descendents of other directories that were also renamed in the send
root to prevent infinite path build loops, we were doing it in cases
where this was not needed and was actually harmful resulting in
infinite path build loops as we
On Wed, Mar 25, 2015 at 6:58 PM, Jeff Mahoney je...@suse.com wrote:
This test tests three conditions where orphan items need to be cleaned up:
1) Default subvolume is fs tree root (mkfs default)
2) Default subvolume has been set explicitly to another subvolume
(set-default)
3) Looking up a
Test a very complex scenario for a btrfs incremental send operation where a
large directory hierarchy had many subtrees moved between parent directories,
preserving the names of some directories and inverting the parent-child
relationship between some directories (a child in the parent snapshot
On Fri, Mar 27, 2015 at 12:07:29AM +, Martin wrote:
Excellent and very rapid packaging, thanks!
Already compiled, installed, and soon to be tried on a test subvolume...
Anyone with any comments on how well duperemove performs for TB-sized
volumes?
On Tue, Mar 24, 2015 at 09:30:52PM -0400, Rich Freeman wrote:
On Mon, Mar 23, 2015 at 7:22 PM, Hugo Mills h...@carfax.org.uk wrote:
On Mon, Mar 23, 2015 at 11:10:46PM +, Martin wrote:
As titled:
Does btrfs have dedup (on raid1 multiple disks) that can be enabled?
The current
commit:
5e8b9e6 btrfs: add regression test for remount with thread_pool resized
did weird things to _filter_mkfs; aside from broken indentation,
it also short-circuited the default non-xfs behavior, which was to
emit a default block inode size. And that was all because btrfs/082
was using
On Fri, Mar 13, 2015 at 12:43:42PM -0700, Omar Sandoval wrote:
On Fri, Mar 13, 2015 at 12:04:30PM +0100, David Sterba wrote:
On Wed, Mar 11, 2015 at 09:40:17PM -0700, Omar Sandoval wrote:
Ping. For anyone following along, it looks like commit cc87317726f8
(mm: page_alloc: revert
On 3/26/15 10:34 PM, Eryu Guan wrote:
Just FYI.
I think generic/204 is a test case issue, _filter_mkfs failed to print
isize and dbsize for btrfs and test failed because of divide by zero
error.
--- /dev/fd/632015-03-25 12:17:05.987107715 -0400
+++ results/generic/204.out.bad
Harald suggested that we remove the message from the fake fsck.btrfs
that some distros run at boot:
https://bugzilla.redhat.com/show_bug.cgi?id=1206502
This output does not add anything, but is a disturbing element of
booting up a system. It's the only message I get, when starting my
system,
14 matches
Mail list logo
