Original Message
Subject: du vs qgroup
From: Ian Hinder
To:
Date: 2015年05月27日 07:04
Hi,
I have a 350 GB btrfs filesystem in which I am storing backups of virtual machine disk images. These are rsynced
periodically from the VM host to a "current" subvolume, followed by a
Hi,
I have a 350 GB btrfs filesystem in which I am storing backups of virtual
machine disk images. These are rsynced periodically from the VM host to a
"current" subvolume, followed by a snapshot operation to a dated subvolume.
One disk image is about 50 GB in size, as reported by ls -l and d
On Mon, May 25, 2015 at 06:06:20PM +0200, Felix Koop wrote:
> Hello,
>
> I have a RAID5 filesystem where one disk has crashed. Now the filesystem is
> not
> recognized any more. Any help available?
>
> Here is some info:
>
> root@server:~# uname -a
> Linux server 4.0.0-1-amd64 #1 SMP Debian 4.0
> Qu Wenruo hat am 26. Mai 2015 um 07:56 geschrieben:
>
> > Label: none uuid: 7d4b023a-a1ef-4991-b01d-31e7c4fdfbcf
> > Total devices 3 FS bytes used 213.96GiB
> > devid 2 size 150.00GiB used 108.53GiB path /dev/mapper/Data1vg-afs0
> > devid 4 size 150.00GiB used 108.53GiB path /dev/mapper/D
Oh, thanks for advice, i'll get and attach it.
i.e. as i understand behaviour like it, not expected, cool
2015-05-26 22:49 GMT+03:00 Chris Murphy :
> Without a complete dmesg it's hard to say what's going on. The call
> trace alone probably don't show the instigating factor so you may need
> to us
Without a complete dmesg it's hard to say what's going on. The call
trace alone probably don't show the instigating factor so you may need
to use remote ssh with journalctl -f, or use netconsole to
continuously get kernel messages prior to the implosion.
Chris Murphy
--
To unsubscribe from this li
Oh, i missing, i've test it on 3.19+ kernels
I can get trace from screen if it interesting for developers.
2015-05-26 14:23 GMT+03:00 Timofey Titovets :
> Hi list,
> I'm regular on this list and I very like btrfs, I want use it on production
> server, and I want replace hw raid on it.
>
> Test ca
On Tue, May 26, 2015 at 12:50 PM, Calvin Walton
wrote:
> On Tue, 2015-05-26 at 12:18 -0600, Chris Murphy wrote:
>> Oh yeah easy to miss, but obvious once pointed out:
>>
>> > Data, single: total=227.94GiB, used=58.16GiB
>>
>> I thought we had automatic deallocation of unused chunks but I guess
>>
On Tue, 26 May 2015 12:18:40 -0600, Chris Murphy wrote:
> Oh yeah easy to miss, but obvious once pointed out:
>
>> Data, single: total=227.94GiB, used=58.16GiB
>
> I thought we had automatic deallocation of unused chunks but I guess
> it hasn't landed yet.
It did (in 3.18 IIRC), but that doesn'
On Tue, 2015-05-26 at 12:18 -0600, Chris Murphy wrote:
> Oh yeah easy to miss, but obvious once pointed out:
>
> > Data, single: total=227.94GiB, used=58.16GiB
>
> I thought we had automatic deallocation of unused chunks but I guess
> it hasn't landed yet.
We do have automatic deallocation of un
Oh yeah easy to miss, but obvious once pointed out:
> Data, single: total=227.94GiB, used=58.16GiB
I thought we had automatic deallocation of unused chunks but I guess
it hasn't landed yet.
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a m
On Tue, May 26, 2015 at 08:36:34PM +0300, Lennert Buytenhek wrote:
> Hi!
>
> The btrfs filesystem on my newly installed laptop has managed to
> hose itself rather thoroughly, and it's now in a state where it
> works okay if you don't write too much to it, but if you do, it
> starts returning -ENOS
On Tue, May 26, 2015 at 11:50:00AM -0600, Chris Murphy wrote:
> Before wiping I suggest making an image with btrfs-image. And then
> also see if any additional messages appear with the enospc_debug mount
> option. And also see if there's any correlation between the journald
> reported failures (th
Before wiping I suggest making an image with btrfs-image. And then
also see if any additional messages appear with the enospc_debug mount
option. And also see if there's any correlation between the journald
reported failures (the specific .journal file) and whether it's +C by
using lsattr. Fedora 2
Hi!
The btrfs filesystem on my newly installed laptop has managed to
hose itself rather thoroughly, and it's now in a state where it
works okay if you don't write too much to it, but if you do, it
starts returning -ENOSPC on a random subset of your filesystem
operations until you let it cool down
The subject should reflect the problem being fixed.
On Fri, May 22, 2015 at 01:46:54PM +0800, Zhaolei wrote:
> From: Zhao Lei
>
> xfstests btrfs/070 sometimes failed.
> In my test machine, its fail rate is about 30%.
> In another vm(vmware), its fail rate is about 50%.
>
> Reason:
> btrfs/070 d
On Mon, May 11, 2015 at 12:58:11AM -0700, Omar Sandoval wrote:
> A user reported on Bugzilla that they were seeing kernel BUGs when
> attempting to replace a missing device on a RAID 6 array. After
> identifying the apparent cause of the BUG, I reached the conclusion that
> there wasn't a quick fix
On Mon, May 25, 2015 at 05:30:14PM +0800, Liu Bo wrote:
> read_tree_block may take a reference on the 'eb', a following
> free_extent_buffer is necessary.
>
> Signed-off-by: Liu Bo
Reviewed-by: David Sterba
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of
On Mon, May 25, 2015 at 05:30:15PM +0800, Liu Bo wrote:
> The return value of read_tree_block() can confuse callers as it always
> returns NULL for either -ENOMEM or -EIO, so it's likely that callers
> parse it to a wrong error, for instance, in btrfs_read_tree_root().
>
> This fixes the above iss
I'm not really understanding the use case. Is this for one time copy
of a Btrfs file system or a need to keep the copies in sync? Because
this sounds like a better fit for rsync, btrfs send/receive, or drdb.
The part especially where I'm getting confused is where you say "start
copying blocks of s
On Fri, May 15, 2015 at 02:36:35PM +0800, Qu Wenruo wrote:
> This bug is found by making break point after change_fsid_prepare() and
> then kill the unfinished change, then try to restore the unfinished fsid
> change.
>
> If fsid change is canceled, open_ctree will still fail even with
> IGNORE_FS
On Fri, May 15, 2015 at 02:28:23PM +0800, Qu Wenruo wrote:
> Change the change_uuid():
> 1) Remove new_chunk_tree_uuid para
> As chunk_tree_uuid is only internal used, no need to manual specify it.
> Use random generated UUID instead.
>
> 2) Don't use heap allocated memory for fs_info->new_fsid/ch
On Tue, May 19, 2015 at 10:21:04AM -0400, Josef Bacik wrote:
> Sometimes we need to test what happens when we're missing a csum for a range,
> so
> add an option to btrfs-corrupt-block to be able to remove a csum range.
> Thanks,
>
> Signed-off-by: Josef Bacik
Applied, thanks.
--
To unsubscri
On Thu, May 21, 2015 at 06:42:29PM +0300, jekarl...@gmail.com wrote:
> From: Emil Karlson
>
> This will fix breakage, when doing chrooted receive with cloned paths
> outside main subvolume.
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of
On Tue, May 26, 2015 at 09:29:25AM +, sri wrote:
> Hugo Mills carfax.org.uk> writes:
>
> >
> > On Tue, May 26, 2015 at 08:45:06AM +, sri wrote:
> > > Hi,
> > >
> > > According to btrfs wiki page, under "Stability status" it is written
> that
> > >
> > > "The filesystem disk format is
Hugo Mills carfax.org.uk> writes:
>
> On Tue, May 26, 2015 at 08:45:06AM +, sri wrote:
> > Hi,
> >
> > According to btrfs wiki page, under "Stability status" it is written
that
> >
> > "The filesystem disk format is no longer unstable".
> >
> > Does this mean if there are more I/Os are g
On Mon, May 25, 2015 at 09:41:04AM -0500, Anthony Plack wrote:
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -117,6 +117,10 @@ static int btrfs_init_inode_security(struct
> btrfs_trans_handle *trans,
> err = btrfs_init_acl(trans, inode, dir);
> if (!err)
>
Hi list,
I'm regular on this list and I very like btrfs, I want use it on production
server, and I want replace hw raid on it.
Test case: server with N scsi discs
2 SAS disks used for raid 1 root fs
If I just remove one disk physically, all okay, kernel show me write errors and
system continue w
On 05/26/2015 08:33 AM, Josh Boyer wrote:
> On Fri, May 22, 2015 at 9:14 PM, Chris Mason wrote:
>> Hi Linus,
>>
>> My for-linus-4.1 branch has three more fixes:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
>> for-linus-4.1
>>
>> I fixed up a regression from 4.0 where
On Fri, May 22, 2015 at 9:14 PM, Chris Mason wrote:
> Hi Linus,
>
> My for-linus-4.1 branch has three more fixes:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
> for-linus-4.1
>
> I fixed up a regression from 4.0 where conversion between different raid
> levels would som
From: Filipe Manana
Zygo Blaxell and other users have reported occasional hangs while an
inode is being evicted, leading to traces like the following:
[ 5281.972322] INFO: task rm:20488 blocked for more than 120 seconds.
[ 5281.973836] Not tainted 4.0.0-rc5-btrfs-next-9+ #2
[ 5281.974818]
On Tue, May 26, 2015 at 08:45:06AM +, sri wrote:
> Hi,
>
> According to btrfs wiki page, under "Stability status" it is written that
>
> "The filesystem disk format is no longer unstable".
>
> Does this mean if there are more I/Os are going on a btrfs file system,
> copy of entire disk (all
Hi,
According to btrfs wiki page, under "Stability status" it is written that
"The filesystem disk format is no longer unstable".
Does this mean if there are more I/Os are going on a btrfs file system,
copy of entire disk (all disk blocks) gives a stable disk?
Just to elaborate more, if btrfs
33 matches
Mail list logo
