On Wed, Apr 08, 2015 at 03:50:04PM +0100, WorMzy Tykashi wrote:
Currently this test uses the system btrfs-image. If there isn't a
btrfs-image on $PATH, the test fails. The test should be using the
locally compiled btrfs-image, not the system one.
Added your sign-off and applied, thanks.
--
To
Hey list,
I've got a problem with resizing a multi drive filesystem.
I had a 5 disk array of 4TB drives. Then I added a 5th (6TB) drive to
the array and replaced one of the 4TB ones with a 6TB drive. As you can
see in my `btrfs fi sh` output below, my newly added drive (ID=6) has
the expected
On Tue, Apr 07, 2015 at 10:34:02PM -0700, Omar Sandoval wrote:
Currently, userspace has no way to know which subvolume is mounted.
Oh, there is a way, 'btrfs inspect-internal rootid /path/to/mount', just
we'd like to see it in the mount options as well.
But,
now that we're guaranteed to have
Now that we're guaranteed to have a meaningful root dentry, we can just
export seq_dentry() and use it in btrfs_show_options(). The subvolume ID
is easy to get and can also be useful, so put that in there, too.
Signed-off-by: Omar Sandoval osan...@osandov.com
---
fs/btrfs/super.c | 4
There's nothing to stop a user from passing both subvol= and subvolid=
to mount, but if they don't refer to the same subvolume, someone is
going to be surprised at some point. Error out on this case, but allow
users to pass in both if they do match (which they could, for example,
get out of
If a directory inode is orphanized, because some inode previously
processed has a new name that collides with the old name of the current
inode, we need to check if it needs its rename operation delayed too,
as its ancestor-descendent relationship with some other inode might
have been reversed
Test btrfs incremental send after renaming and moving directories around in a
way that ends up making a directory have different dentries with the same name
but pointing to different inodes in the parent and send snapshots, and also
inverting the ancestor-descendent relationship between one of
Hi,
On Sun, May 18, 2014 at 03:28:18PM +1000, Paul Harvey wrote:
This is a Damnit! I held the power button in and now it won't mount! story,
but I'm sharing what I found to learn what I can. And in case it's useful for
btrfs development.
Also curious if my usage of Docker (an LXC thing,
Original Message
Subject: Re: snapshot space use
From: Piotr Szymaniak szar...@grubelek.pl
To: Qu Wenruo quwen...@cn.fujitsu.com
Date: 2015年04月09日 17:02
On Thu, Apr 09, 2015 at 08:45:21AM +0800, Qu Wenruo wrote:
*snip*
NOTE: quota is not so stable and has some problem, but
Another way to put this is, the only reliable way to mount and get
subvolume info in findmnt and /proc is by using subvol=.
When using subvolid=, the subvolume info isn't available unless the
initial mount is the top level (ID 5).
--
Chris Murphy
--
To unsubscribe from this list: send the line
kernel-4.0.0-0.rc6.git0.1.fc22.i686
The short version is that if the top level subvolume is not mounted
first, any usage of subvolid= fails to show the subvolume in either
findmnt or /proc/self/mountinfo.
That is, only when the initial mount is the top level, any subsequent
mount using option
Thank you for trying btrfs, it's great for snapshots in docker, but
outside of the 2 helpful comments you already got, do yourself a favour
and use a newer kernel.
Btrfs moves fast, and 3.13 is way too old. The number of bugs (including
corruption bugs) that has been fixed since then is too long
On Thu, Apr 9, 2015 at 10:03 AM, André-Sebastian Liebe an...@lianse.eu wrote:
Hey list,
I've got a problem with resizing a multi drive filesystem.
I had a 5 disk array of 4TB drives. Then I added a 5th (6TB) drive to
the array and replaced one of the 4TB ones with a 6TB drive.
You did device
On Thu, Apr 09, 2015 at 01:38:19PM -0600, Chris Murphy wrote:
Another way to put this is, the only reliable way to mount and get
subvolume info in findmnt and /proc is by using subvol=.
When using subvolid=, the subvolume info isn't available unless the
initial mount is the top level (ID 5).
On Sun, May 18, 2014 at 6:28 AM, Paul Harvey csir...@gmail.com wrote:
This is a Damnit! I held the power button in and now it won't mount!
story, but I'm sharing what I found to learn what I can. And in case it's
useful for btrfs development.
Also curious if my usage of Docker (an LXC thing,
Hey.
I wondered whether this is possible in btrfs (or could be
implemented),... it's in a way similar to send/receive, but AFAIU not
fully solvable with that.
What I want to do is making incremental backups of a (btrfs) filesystem
to smaller mediums (that is for example: from a big RAID
On Wed, Apr 08, 2015 at 02:06:14PM +0800, Qu Wenruo wrote:
Original Message
Subject: [PATCH 2/3] Btrfs: unify subvol= and subvolid= mounting
From: Omar Sandoval osan...@osandov.com
To: Chris Mason c...@fb.com, Josef Bacik jba...@fb.com, David Sterba
dste...@suse.cz,
On Thu, Apr 09, 2015 at 06:28:48PM +0200, David Sterba wrote:
On Tue, Apr 07, 2015 at 10:34:01PM -0700, Omar Sandoval wrote:
Currently, mounting a subvolume with subvolid= takes a different code
path than mounting with subvol=. This isn't really a big deal except for
the fact that mounts
On Tue, Apr 07, 2015 at 10:34:01PM -0700, Omar Sandoval wrote:
Currently, mounting a subvolume with subvolid= takes a different code
path than mounting with subvol=. This isn't really a big deal except for
the fact that mounts done with subvolid= or the default subvolume don't
have a dentry
hi,
fscache cannot currently be used with btrfs as the backing store for the
cache (managed by cachefilesd).
This is because cachefiles needs the -bmap address_space_operation, and
btrfs doesn't provide it.
cachefiles only uses this to find out if a particular page is a 'hole' or
not. For
NeilBrown ne...@suse.de wrote:
Is there a better way? Could a better way be created? Maybe
SEEK_DATA_RELIABLE ??
fiemap() maybe?
Also, if you do try to use fscache on btrfs with 3.19, then nothing gets
cached (as expected) and with a heavy load you can lose a race and get an
asserting
Is disabling PRUNE_BIND_MOUNTS for updatedb really the only solution here?
On Fri, Apr 3, 2015 at 1:07 PM, G. Richard Bellamy
rbell...@pteradigm.com wrote:
I've just noticed that I'm having issues with finding files using
locate when those files are on btrfs subvolume mounts.
The issue is
On Thu, 09 Apr 2015 12:08:43 +0800, Dongsheng Yang wrote:
We need to fill inode when we found a node for it in delayed_nodes_tree.
But we did not fill the -last_trans currently, it will cause the test
of xfstest/generic/311 fail. Scenario of the 311 is shown as below:
Problem:
(1).
On Thu, Apr 09, 2015 at 06:14:33PM +0200, Christoph Anton Mitterer wrote:
Hey.
I wondered whether this is possible in btrfs (or could be
implemented),... it's in a way similar to send/receive, but AFAIU not
fully solvable with that.
What I want to do is making incremental backups of a
On Fri, Mar 06, 2015 at 12:03:59PM +1100, Paul Harvey wrote:
Apparently in my haste, forgot to include any information in my email.
This is also in the URL to the gist of my test script:
btrfs v3.17
Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) x86_64 GNU/Linux
# mount:
On Thu, Apr 09, 2015 at 08:45:21AM +0800, Qu Wenruo wrote:
*snip*
NOTE: quota is not so stable and has some problem, but should give
you enough info.
Those are related to actually using quota or can also hit you when you
want to use it just for things like this snapshot space use?
Piotr
On Tue, Apr 7, 2015 at 11:40 PM, Dan Merillat dan.meril...@gmail.com wrote:
Bcache failures are nasty, because they leave a mix of old and new
data on the disk. In this case, there was very little dirty data, but
of course the tree roots were dirty and out-of-sync.
On Thu, Apr 9, 2015 at 1:41 PM, Omar Sandoval osan...@osandov.com wrote:
On Thu, Apr 09, 2015 at 01:38:19PM -0600, Chris Murphy wrote:
Another way to put this is, the only reliable way to mount and get
subvolume info in findmnt and /proc is by using subvol=.
When using subvolid=, the
28 matches
Mail list logo
