Hello Anand,
the
> mount -o degraded <-- this should work
is my problem. The fist times it works but suddently, after a reboot, it fails
with message "BTRFS: too many missing devices, writeable mount is not allowed"
in kernel log.
"btrfs fi show /backup2" shows:
Label: none uuid: 6d755db5-f
Ah thanks David. So its 2 disks RAID1.
Martin,
disk pool error handle is primitive as of now. readonly is the only
action it would take. rest of recovery action is manual. thats
unacceptable in a data center solutions. I don't recommend btrfs VM
productions yet. But we are working to get t
btrfs has a small bug at the moment where balance can't convert raid
levels (it just does nothing), it is meant to be fixed with the next
kernel release.
On Wed, Jun 10, 2015 at 3:28 PM, Guilherme Gonçalves
wrote:
> Hello!, i think i made a mistake
> i had two 3tb drivre on a raid 1 setup, i boug
Hello!, i think i made a mistake
i had two 3tb drivre on a raid 1 setup, i bought two aditional 3tb
drives to make my raid 10 array
i used this commands
btrfs -f device add /dev/sdc /mnt/nas/(i used -f because i
formatted my new drives using gpt)
btrfs -f device add /dev/sdf /mnt/nas/
finally
Anand Jain posted on Wed, 10 Jun 2015 09:19:37 +0800 as excerpted:
> On 06/09/2015 01:10 AM, Martin wrote:
>> Hello!
>>
>> I have a raid1-btrfs-system (Kernel 3.19.0-18-generic, Ubuntu Vivid
>> Vervet, btrfs-tools 3.17-1.1). One disk failed some days ago. I could
>> remount the remaining one with
On Wed, 3 Jun 2015 15:42:39 +0200
Christoph Hellwig wrote:
> Currently we have two different ways to signal an I/O error on a BIO:
>
> (1) by clearing the BIO_UPTODATE flag
> (2) by returning a Linux errno value to the bi_end_io callback
>
> The first one has the drawback of only communicati
On Tue, Jun 09, 2015 at 10:39:49AM +0200, Trollkarlen Marklund wrote:
>
> Hi!
>
> I have a two disk in raid0 where one of the disks have failed. Approximately
> 17Mb cant be read from the disk, due to hardware issues. I made a clone of
> the disk but all 3 superblocks are in the non-readable a
On Tue, Jun 09, 2015 at 01:56:41PM +0100, Filipe David Manana wrote:
> On Tue, Jun 9, 2015 at 1:04 PM, Liu Bo wrote:
> > If we're overwriting an allocated file without changing timestamp
> > and inode version, and the file is with NODATACOW, we don't have any
> > metadata to
> > commit, thus we
On 06/09/2015 01:10 AM, Martin wrote:
Hello!
I have a raid1-btrfs-system (Kernel 3.19.0-18-generic, Ubuntu Vivid Vervet,
btrfs-tools 3.17-1.1). One disk failed some days ago. I could remount the
remaining one with "-o degraded". After one day and some write-operations
(with no errrors) I had t
Original Message
Subject: Re: [GIT PULL] Qgroup rework with other Fujitsu fix.
From: Josef Bacik
To: adam900710
Date: 2015年06月09日 22:54
On 06/09/2015 10:23 AM, adam900710 wrote:
Sorry, forgot to reply to all.
To Josef,
I am afraid that your conclusion is not right, as i
Original Message
Subject: Re: [GIT PULL] Qgroup rework with other Fujitsu fix.
From: Josef Bacik
To: adam900710
Date: 2015年06月09日 22:54
On 06/09/2015 10:23 AM, adam900710 wrote:
Sorry, forgot to reply to all.
To Josef,
I am afraid that your conclusion is not right, as i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/9/15 4:48 PM, Jeff Mahoney wrote:
> On 6/8/15 10:12 AM, Filipe David Manana wrote:
>> On Wed, Jun 3, 2015 at 3:47 PM, wrote:
>>> From: Jeff Mahoney
>>>
>>> When we clear the dirty bits in btrfs_delete_unused_bgs for
>>> extents in the empty b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/8/15 10:12 AM, Filipe David Manana wrote:
> On Wed, Jun 3, 2015 at 3:47 PM, wrote:
>> From: Jeff Mahoney
>>
>> When we clear the dirty bits in btrfs_delete_unused_bgs for
>> extents in the empty block group, it results in
>> btrfs_finish_exten
On Mon, Jun 08, 2015 at 11:48:54AM -0400, Chris Mason wrote:
> On 06/06/2015 02:07 AM, Tomasz Chmielewski wrote:
> > 4.1-rc6, busy filesystem.
> >
> > I was running mongo import which made quite a lot of IO.
> > During the import, I did "chattr +C /var/lib/mongodb" - shortly after I
> > saw this i
Hi,
I've noticed this "@" sign in the subvolume's path with SLES12. I'm
wondering what is its purpose. openSUSE 13.2 doesn't seem to be using
it.
Thanks,
Gábor
SLES12:
# btrfs sub list /
ID 257 gen 2270 top level 5 path @
ID 258 gen 1655 top level 257 path @/boot/grub2/i386-pc
ID 259 gen 4263 t
On 06/09/2015 10:23 AM, adam900710 wrote:
Sorry, forgot to reply to all.
To Josef,
I am afraid that your conclusion is not right, as in the patch, it will
only merge delayed refs when they are in same sequence number.
In fact, in the patch, conditions for merge is even more restrict than
befor
On 06/07/2015 11:06 PM, Qu Wenruo wrote:
Hi Chris,
Please pull the 19 patchset from my branch for_chris_4.2.
We have tested it in a week.
Although it is originally based on 4.1-rc5, not the integration branch.
Quick tests shows no new bugs, although we will rerun the full test,
I'll send the pa
On 06/09/2015 03:17 AM, Qu Wenruo wrote:
> Hi, Chris and Filipe.
>
> Would you consider the patch from Filipe to be merged into 4.2?
>
> [PATCH] Btrfs: avoid syncing log in the fast fsync path when not necessary
>
> https://patchwork.kernel.org/patch/6138811/
>
>
> The performance regression i
On Tue, Jun 9, 2015 at 1:04 PM, Liu Bo wrote:
> If we're overwriting an allocated file without changing timestamp
> and inode version, and the file is with NODATACOW, we don't have any metadata
> to
> commit, thus we can just flush the data device cache and go forward.
>
> However, if there's ha
Read-ahead is done for the pages in the range [ra_index, ra_index + cluster -
1]. So the next read-ahead should be starting from the page at index 'ra_index
+ cluster' (unless we deemed that the extent at 'ra_index + cluster' as
non-defraggable) rather than from the page at index 'ra_index +
max_cl
MS_I_VERSION is enabled by default for btrfs, this adds an alternative
option to toggle it off.
Signed-off-by: Liu Bo
---
fs/btrfs/super.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index f2c9f9d..c81a3f1 100644
--- a/fs/btrfs/su
If we're overwriting an allocated file without changing timestamp
and inode version, and the file is with NODATACOW, we don't have any metadata to
commit, thus we can just flush the data device cache and go forward.
However, if there's have any change on extents' disk bytenr, inode size,
timestam
On Tue, May 26, 2015 at 06:08:20PM +, Hugo Mills wrote:
> > 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
On Tue, Jun 9, 2015 at 11:04 AM, Robbie Ko wrote:
> Hi Filipe,
>
> 2015-06-08 22:00 GMT+08:00 Filipe David Manana :
>> On Mon, Jun 8, 2015 at 4:44 AM, Robbie Ko wrote:
>>> Hi Filipe,
>>
>> Hi Robbie,
>>
>>>
>>> I've fixed "don't send utimes for non-existing directory" with another
>>> solution.
Hi Filipe,
2015-06-08 22:00 GMT+08:00 Filipe David Manana :
> On Mon, Jun 8, 2015 at 4:44 AM, Robbie Ko wrote:
>> Hi Filipe,
>
> Hi Robbie,
>
>>
>> I've fixed "don't send utimes for non-existing directory" with another
>> solution.
>>
>> In apply_dir_move(), the old parent dir. and new parent d
When testing under libguestfs, btrfs-convert will never succeed to fix
chunk map, and always fails.
But in that case, it's already a mountable btrfs.
So better to info user with different error message for that case.
The root cause of it is still under investigation.
Signed-off-by: Qu Wenruo
--
Hi!
I have a two disk in raid0 where one of the disks have failed. Approximately
17Mb cant be read from the disk, due to hardware issues. I made a clone of the
disk but all 3 superblocks are in the non-readable areas :(
So my question is, is there any tool to recreate the superblock from the
Hi, Chris and Filipe.
Would you consider the patch from Filipe to be merged into 4.2?
[PATCH] Btrfs: avoid syncing log in the fast fsync path when not necessary
https://patchwork.kernel.org/patch/6138811/
The performance regression is already in 4.1, and I really don't like to
see the perform
Hi Qu,
Hi Chris,
Please pull the 19 patchset from my branch for_chris_4.2.
We have tested it in a week.
Although it is originally based on 4.1-rc5, not the integration branch.
Quick tests shows no new bugs, although we will rerun the full test,
I'll send the patchset first for your reviewing:
29 matches
Mail list logo
