> > On Thu 131024, Chris Murphy wrote:
> >>
> >> On Oct 24, 2013, at 4:46 PM, Karl Kiniger wrote:
> >
> > Still hoping there is a better way on btrfs than sending and receiving the
> > snaps
> > just to a different folder.
>
> Presumably you can rename/move the containing folder. So if it
As we know, a new fs doesn't have space cache, so we set the cache generation
of the super block to be -1ULL, it is not equal to the fs generation. But the
check program didn't consider this case, and output the following message
cache and super generation don't match, space cache will be inval
After running space balance on a new fs, the fs check program outputed the
following warning message:
free space inode generation (0) did not match free space cache generation (20)
Steps to reproduce:
# mkfs.btrfs -f
# mount
# btrfs balance start
# umount
# btrfs check
It was because
On 10/25/2013 05:52 AM, Timofey Titovets wrote:
Hello, i suggest temporary solution to use swap file under btrfs.
I test it, and it work good.
I invent simple the way, how create and using swap file, just see
following sh code:
swapfile=$(losetup -f) #free loop device
truncate -s 8G /swap #cr
On Thu, Oct 24, 2013 at 03:31:55PM -0500, Mitch Harder wrote:
> On Tue, Sep 17, 2013 at 10:21 AM, David Sterba wrote:
> > The command has been moved and we should rename the files accordingly,
> > so the entry point is now in cmds-rescue.c and the core functionality
> > in it's own file.
> >
> > R
On Thu, 24 Oct 2013 23:52:01 +0300
Timofey Titovets wrote:
> Hello, i suggest temporary solution to use swap file under btrfs.
> I test it, and it work good.
>
> I invent simple the way, how create and using swap file, just see
> following sh code:
>
> swapfile=$(losetup -f) #free loop device
>
On Fri, Oct 25, 2013 at 04:35:46PM +0600, Roman Mamedov wrote:
> On Thu, 24 Oct 2013 23:52:01 +0300
> Timofey Titovets wrote:
>
> > Hello, i suggest temporary solution to use swap file under btrfs.
> > I test it, and it work good.
> >
> > I invent simple the way, how create and using swap file,
We define a 'int' to get extent's generation by mistake,fix it.
Signed-off-by: Wang Shilong
---
fs/btrfs/relocation.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
index a945374..c166740 100644
--- a/fs/btrfs/relocation.c
+++ b/
Originally, we introduced scrub_super_lock to synchronize
tree log code with scrubbing super.
However we can replace scrub_super_lock with device_list_mutex,
because writing super will hold this mutex, this will reduce an extra
lock holding when writing supers in sync log code.
Signed-off-by: Wan
Hello insiders
is there low level support to change inode ctimes somehow?
(on ext[234] it can be done using debugfs)
It would be nice to make received snapshots as similar as
possible to their send source. (I am not talking about
uuids and such, just ls -lc output)
creative ideas are welcome,
K
I was reading the other messages in the mailing list, and tried the
advice on http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg27524.html
I checked out the latest code, did a make of the btrfs-tools
# sudo btrfs rescue chunk-recover -vy /dev/sda1
All Devices:
Device: id = 1, nam
John Goerzen complete.org> writes:
>
> On 10/20/2013 09:51 AM, Tomasz Chmielewski wrote:
> > I'll do some more tests with lots of extents to see if it's
> > reproducible here as well.
> >
> >
> Interestingly, I've generally had qgroups enabled here as well, possibly
> on all of these systems.
Hello,
This is an x86_64 box running 3.10. It is presently running restore from
the e2fs dump/restore, restoring a dump made on an ext4 system onto a btrfs
filesystem. The btrfs filesystem is the only btrfs filesystem mounted on
the machine, and it is mounted with only the noatime mount option.
Apparently we don't actually close the files until we return to userspace, so
stop using vfs_read in send. This is actually better for us since we can avoid
all the extra logic of holding the file we're sending open and making sure to
clean it up. This will fix people who have been hitting too ma
need fsinfo from btrfs-control that is when mount path is
not known.
current method of going through each mount points isn't
efficient, and multiple subvol of a fsid could be mounted
means extra logic to handle that. Further this will help
to revamp check_mounted() (planned)
as of now with out this patch user would see
fsinfo per btrfs mount path but which mean multiple
entry if more than one subvol is mounted of the same
fsid. so this patch will handle that nicely.
Signed-off-by: Anand Jain
---
cmds-filesystem.c | 90 +-
This adds ioctl BTRFS_IOC_GET_FSIDS which reads the fs
info through the btrfs-control
Signed-off-by: Anand Jain
---
fs/btrfs/super.c | 47 ++-
fs/btrfs/volumes.c | 33 ++
fs/btrfs/volumes.h |2 +
Unfortunately you can't run --init-extent-tree if you can't actually read the
extent root. Fix this by allowing partial starts with no extent root and then
have fsck only check to see if the extent root is uptodate _after_ the check to
see if we are init'ing the extent tree. Thanks,
Signed-off-b
On 25/10/13 19:01, Josef Bacik wrote:
> Unfortunately you can't run --init-extent-tree if you can't actually read the
> extent root. Fix this by allowing partial starts with no extent root and then
> have fsck only check to see if the extent root is uptodate _after_ the check
> to
> see if we are
On Fri, Oct 25, 2013 at 07:27:24PM +0100, Martin wrote:
> On 25/10/13 19:01, Josef Bacik wrote:
> > Unfortunately you can't run --init-extent-tree if you can't actually read
> > the
> > extent root. Fix this by allowing partial starts with no extent root and
> > then
> > have fsck only check to
Hi I have similar (not same) problem like described here:
http://www.spinics.net/lists/linux-btrfs/msg27102.html
So I want just make Josef to have some fun seeing btrfs-image of unmountable
filesystem, before btrfs-zero-log command...
Two images and explanatory text is available on here:
http:
We can just return an error and we'll bail out properly. We still want to catch
this case to make sure we don't have a bug somewhere, so just warn if this pops
up. Thanks,
Signed-off-by: Josef Bacik
---
fs/btrfs/inode.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs
I noticed that if the free space cache has an error writing out it's data it
won't actually error out, it will just carry on. This is because it doesn't
check the return value of btrfs_wait_ordered_range, which didn't actually return
anything. So fix this in order to keep us from making free spac
This is just the write path, the only reason we start a transaction is so we can
check cross references, we don't make any actual changes, so there is no reason
to abort the transaction if we fail. Thanks,
Signed-off-by: Josef Bacik
---
fs/btrfs/inode.c | 20 +---
1 file changed
My publishing patchset added the ability for the kernel to report
the size of the global metadata reservation via ioctl and sysfs.
This test confirms that we get sane results on an empty file system.
ENOTTY and missing /sys/fs/btrfs//allocation are not considered
failures.
Signed-off-by: Jeff Ma
This tests the exporting of feature information from the kernel via
sysfs and ioctl. The first test works whether the sysfs permissions
are correct, if the information exported via sysfs matches
what the ioctls are reporting, and if they both match the on-disk
superblock's version of the feature se
These are the tests that Josef requested accompany the submission of
the btrfs publishing/export patchset[1].
100: Test new global metadata reservation ioctl
101: Test new sysfs exporting of allocation and device membership
102: Test new sysfs exporting of feature bits
103: Test setting/clearing f
This tests the sysfs publishing for btrfs allocation and device
membership info under a number of different layouts, similar to the
btrfs replace test. We test the allocation files only for existence and
that they contain numerical values. We test the device membership
by mapping the devices used t
On 10/25/13, 4:52 PM, Jeff Mahoney wrote:
> These are the tests that Josef requested accompany the submission of
> the btrfs publishing/export patchset[1].
>
> 100: Test new global metadata reservation ioctl
> 101: Test new sysfs exporting of allocation and device membership
> 102: Test new sysfs
Just saw this with 3.12-rc6:
[57459.603773] [ cut here ]
[57459.603798] WARNING: CPU: 6 PID: 30148 at fs/btrfs/ctree.c:1322
btrfs_search_old_slot+0x338/0x81d [btrfs]()
[57459.603812] Modules linked in: veth ipt_MASQUERADE iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_na
when I use two disk to create raid0 in btrfs, after rebooting
system,one disk unable to mount ,
error is as follows:
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
you can change a "ro" snapshot into a "rw" snapshot
you just snapshot it without the -r" option
ex:
# btrfs subv snap -r linux-3.12-rc5 snap_ro
Create a readonly snapshot of 'linux-3.12-rc5' in './snap_ro'
# touch ./snap_ro/helo
touch: cannot touch ‘./snap_ro/helo’: Read-only file system
# bt
32 matches
Mail list logo
