On 09/21/2013 04:33, Josef Bacik wrote:
Users have been complaining of the uuid tree stuff warning that there is no uuid
root when trying to do snapshot operations. This is because if you mount -o ro
we will not create the uuid tree. But then if you mount -o rw,remount we will
still not create
From: Wang Shilong wangsl.f...@cn.fujitsu.com
Until now if one of device's first superblock is corrupt,btrfs will
fail to mount. Luckily, btrfs have at least two superblocks for
every disk.
In theory, if silent corrupting happens when we are writting superblocks
into disk, we must hold at least
Am Freitag, 20. September 2013, 22:34:15 schrieb Josef Bacik:
On Sat, Sep 21, 2013 at 12:25:02AM +0200, Martin Steigerwald wrote:
Hi!
I tried to create a snapshot today like this:
merkaba:/mnt/debian-zeit ls -l
insgesamt 0
drwxr-xr-x 1 root root 210 Sep 20 11:48 root
Am Samstag, 21. September 2013, 10:54:55 schrieb Martin Steigerwald:
Am Freitag, 20. September 2013, 22:34:15 schrieb Josef Bacik:
On Sat, Sep 21, 2013 at 12:25:02AM +0200, Martin Steigerwald wrote:
Hi!
I tried to create a snapshot today like this:
merkaba:/mnt/debian-zeit ls
You will want the patch I just sent,
Btrfs: create the uuid tree on remount rw
and that should fix the snapshot problems. Thanks,
thanks Josef - you can close this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=61301
then. will try your patch later, too.
Ahmet
--
To unsubscribe from
On 09/18/2013 10:51 PM, David Sterba wrote:
On Wed, Sep 18, 2013 at 09:11:01AM +0800, rongqing...@windriver.com wrote:
From: Roy Li rongqing...@windriver.com
The dependencies of all: version.h or other similar ones can not
fix the parallel build failure, only reduce the times; In fact,
many
Similar to ocfs2, btrfs also supports that extents can be shared by
different inodes, and there are some userspace tools requesting
for this kind of 'space shared infomation'.[1]
ocfs2 uses flag FIEMAP_EXTENT_SHARED, so does btrfs.
[1]:
