On 12 April 2018 at 00:25, Qu Wenruo wrote:
> I'm curious about what's the underlying disk?
It's an Samsung PM951 NVMe SSD.
> Is it plain physical device? Or have other layers like bcache/lvm?
btrfs on LUKS
>> btrfs check
> Full output please.
https://gist.githubusercontent.com/tlvince/acf51b
My btrfs laptop had a power outage and failed to boot with "parent
transid verify failed..." errors. (I have backups).
I couldn't rw mount on a live disk, but could ro mount. I tried btrfs
scrub and then btrfs check --repair to no avail. However, btrfs rescue
zero-log _did_ work; the drive can be
On 19/09/16 19:41 +0200, David Sterba wrote:
Applied, thanks. I wonder where the original argument got lost. In the
commit 2ed161bd281beca29feebebbc8c4227cc6e918c3 it to added to getopt
but inside cmd_subvol_create. I'll fix it as well.
Not sure. I found it while investigating feasibility of ad
Exposing the verbose flag that already had the logic for verbose output
Vincent Batts (1):
btrfs-progs: subvolume verbose delete flag
cmds-subvolume.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
2.9.0
--
To unsubscribe from this list: send the line "unsubscribe linux-
There was already the logic for verbose output, but the flag parsing did
not include it.
Signed-off-by: Vincent Batts
---
cmds-subvolume.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/cmds-subvolume.c b/cmds-subvolume.c
index e7ef67d..f8c9f48 100644
--- a/cmds
Add missing comparison to op in expression, which was forgotten when doing
the REQ_OP transition.
Fixes: b3d3fa519905 ("btrfs: update __btrfs_map_block for REQ_OP transition")
Signed-off-by: Vincent Stehlé
Cc: Mike Christie
Cc: Jens Axboe
---
Hi,
I saw that issue in linux next.
N
Make sure to deallocate fspath with vfree() in case of error in
init_ipath().
fspath is allocated with vmalloc() in init_data_container() since
commit 425d17a290c0 ("Btrfs: use larger limit for translation of logical to
inode").
Signed-off-by: Vincent Stehlé
Cc: Chris Mason
Cc: Josef
> On Nov 26, 2015, at 10:03 PM, Vincent Olivier wrote:
>
>>
>> On Nov 25, 2015, at 8:44 PM, Qu Wenruo wrote:
>>
>>
>>
>> Vincent Olivier wrote on 2015/11/25 11:51 -0500:
>>> I should probably point out that there is 64GB of RAM on this mac
> On Nov 25, 2015, at 8:44 PM, Qu Wenruo wrote:
>
>
>
> Vincent Olivier wrote on 2015/11/25 11:51 -0500:
>> I should probably point out that there is 64GB of RAM on this machine and
>> it’s a dual Xeon processor (LGA2011-3) system. Also, there is only Btrfs
the middle of the
night when zero (0) client was connected.
You will find below the full “btrfs check” log for each device in the order it
is listed by “btrfs fi show”.
Ca I get a strong confirmation that I should run with the “—repair” option on
each device? Thanks.
Vincent
Checking
Hi,
Woke up this morning with a kernel panic (for which I do not have details).
Please find below the output for btrfs check. Is this normal ? What should I do
? Arch Linux 4.2.5. Btrfs-utils 4.3.1. 17x4TB RAID10.
Regards,
Vincent
[root@3dcpc5 ~]# btrfs check /dev/sdk
Checking filesystem on
Fix a check of len versus PATH_MAX in function copy_symlink(), to
account for the terminating null byte.
Resolves-Coverity-CID: 1296749
Signed-off-by: Vincent Stehlé
---
cmds-restore.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmds-restore.c b/cmds-restore.c
index
> On Sep 16, 2015, at 2:22 PM, Austin S Hemmelgarn wrote:
>
> On 2015-09-16 12:51, Vincent Olivier wrote:
>> Hi,
>>
>>
>>> On Sep 16, 2015, at 11:20 AM, Austin S Hemmelgarn
>>> wrote:
>>>
>>> On 2015-09-16 10:43, M G Berberich
performance jitter are valid however, as are
> the complaints of apparent CPU intensive stalls in the BTRFS code, and I
> occasionally see both on my own systems.
Me too. My two cents is that focusing on improving performances for
Btrfs-optimal use cases is much more interesting than bringing ne
It's ~900GiB. Sorry.
I'm on 4.1.6 Arch Linux.
-Original Message-
From: "Duncan" <1i5t5.dun...@cox.net>
Sent: Tuesday, September 1, 2015 03:30
To: linux-btrfs@vger.kernel.org
Subject: Re: errors while "btrfs receive"
Vincent Olivier posted on Mon, 31
hi,
i'm doing a ~900TiB receive on a 6x4TB RAID0
"fi show", "device scan" all fail and report "unable to connect to /dev/sdX"
is it normal ?
thanks,
Vincent
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body o
ces for the features discussed
(multi-device GOTCHAS should link to multi-device HOWTO).
I will be thinking about it more before doing anything and still welcoming
ideas.
Thanks !
Vincent
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to
y.
For my own sake and other's I would like to maintain (if nobody is already
working on that nor needs any help) a centralized human-readable digest of
known issues that would be featured prominently on top of the Btrfs wiki. I
would merge the Gotchas page and the various known issues pages (in
nd familiar ? I thought I was safe with uuid mount in stab…
I can (temporarily) live with manually mounting this filesystem but I would
appreciate being able to mount it at boot time via fstab…
thanks
vincent
-Original Message-
From: "Vincent Olivier"
Sent: Thursday, August 13,
I'll try without autodefrag anyways tomorrow just to make sure.
And then file a bug report too with however it decides to behave.
Vincent
-Original Message-
From: "Duncan" <1i5t5.dun...@cox.net>
Sent: Thursday, August 13, 2015 20:30
To: linux-btrfs@vger.kernel.o
I have 2 snapshots a few days apart for incrementally backing up the volume but
that's it.
I'll try without autodefrag tomorrow.
Vincent
-Original Message-
From: "Chris Murphy"
Sent: Thursday, August 13, 2015 19:19
To: "Btrfs BTRFS"
Subject: Re: mount
he problem when I mount manually without the
"noauto,x-systemd.automount" options.
Can anyone help ?
Thanks.
Vincent
-Original Message-
From: "Austin S Hemmelgarn"
Sent: Wednesday, August 5, 2015 07:30
To: "John Ettedgui"
Cc: "Qu Wenruo" , &q
I forgot to say: I'm with Centos 7 and Kernel 4.1.3 but it's been doing this
since Kernel 4.0, the time at which I started using btrfs.
thanks
-Original Message-----
From: "Vincent Olivier"
Sent: Friday, July 24, 2015 14:41
To: linux-btrfs@vger.kernel.org
Subject:
that. Is there a way to increase the timer or something ?
Thanks,
Vincent
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
this is GOOD news . thanks !
> On Jul 10, 2015, at 3:11 PM, Hugo Mills wrote:
>
> On Fri, Jul 10, 2015 at 03:03:27PM -0400, Vincent Olivier wrote:
>> actually I have another question : is it posssible for a RAID0 fs to
>> “receive” from a “sending” RAID10 ?
>
>
actually I have another question : is it posssible for a RAID0 fs to “receive”
from a “sending” RAID10 ? or do they need to be of the same replication scheme
too ?
> On Jun 27, 2015, at 10:34 AM, Vincent Olivier wrote:
>
> ok i’ll go home and rethink my life then ;)
>
>&g
ok i’ll go home and rethink my life then ;)
> On Jun 27, 2015, at 10:21 AM, Hugo Mills wrote:
>
> On Sat, Jun 27, 2015 at 10:04:28AM -0400, Vincent Olivier wrote:
>> Hi,
>>
>> There are 4 things I’m not sure about re:send/receive.
>>
>> 1) Is it possibl
eive if at all ?
4) If a file is created, modified and then deleted in-between two snapshots is
it ignored by send/receive or does send/receive "re-enacts” the journal exactly
?
Thanks,
Vincent--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the bo
> On Jun 16, 2015, at 7:58 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>
> Vincent Olivier posted on Tue, 16 Jun 2015 09:34:29 -0400 as excerpted:
>
>
>>> On Jun 16, 2015, at 8:25 AM, Hugo Mills wrote:
>>>
>>> On Tue, Jun 16, 2015 at 08:09:17AM -
> On Jun 17, 2015, at 9:27 AM, Hugo Mills wrote:
>
> On Wed, Jun 17, 2015 at 09:13:08AM -0400, Vincent Olivier wrote:
>>
>>> On Jun 16, 2015, at 8:14 PM, Chris Murphy wrote:
>>>
>>> On Tue, Jun 16, 2015 at 5:58 PM, Duncan <1i5t5.dun...@cox.net
> On Jun 16, 2015, at 8:14 PM, Chris Murphy wrote:
>
> On Tue, Jun 16, 2015 at 5:58 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>
>> On a current kernel unlike older ones, btrfs actually automates entirely
>> empty chunk reclaim, so this problem doesn't occur anything close to near
>> as often as
>
> On Jun 16, 2015, at 8:25 AM, Hugo Mills wrote:
>
> On Tue, Jun 16, 2015 at 08:09:17AM -0400, Vincent Olivier wrote:
>>
>> "btrfs filesystem df” gives :
>>
>>
>> Data, RAID10: total=7.08TiB, used=7.02TiB
>> Data, single: total=8.00M
(long test, short test) btrfs RAID
devices?
Thanks!
Vincent
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
t 0, gen 0
[ 374.253555] BTRFS: too many missing devices, writeable mount is not allowed
[ 374.332474] BTRFS: open_ctree failed
and, yes, data + metadata are raid10
--
Vincent
On Sat, Oct 18, 2014 at 6:37 AM, Anand Jain wrote:
>
> somethings aren't matching well. the issue is..
>
>
Hi !
I have a faulty drive in my raid10 and want it to be replaced.
Working drive are xvd[bef] and replacement drive is xvdc.
When I mount my drive in RW:
#mount -odegraded /dev/xvdb /tank
#dmesg -c
[ 6207.294513] btrfs: device fsid 728ef4d8-928c-435c-b707-f71c459e1520
devid 1 transid 551398 /dev
When things go wrong for lzo-compressed btrfs, feeding lzo1x_decompress_safe()
with corrupt data during restore can lead to crashes. Reduce the risk by adding
a check on the input length.
Signed-off-by: Vincent Stehlé
---
Hi,
This patch actually allowed me to finish a btrfs restore of a
Shit, I've followed the official documentation
https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices#Replacing_failed_devices
With, as explain:
mkfs.btrfs -d single /dev/sda3 /dev/sdb1 /dev/sdc1 /dev/sdd1
mount -o degraded /dev/sda3 /media/single-raid/
btrfs device delete mi
Le 13/05/2013 16:29, Harald Glatt a écrit :
On Mon, May 13, 2013 at 4:15 PM, Vincent wrote:
Hello,
I am on Ubuntu Server 13.04 with Linux 3.8.
I've created a "single-raid" using /dev/sd{a,b,c,d}{1,3}. One of my hard
drives has failed, I mean it's materially dead.
:~$ s
Hello,
I am on Ubuntu Server 13.04 with Linux 3.8.
I've created a "single-raid" using /dev/sd{a,b,c,d}{1,3}. One of my hard
drives has failed, I mean it's materially dead.
:~$ sudo btrfs filesystem show
Label: none uuid: 40886f51-8c9b-4be1-8721-83bf5653d2a0
Total devices 5 FS bytes used
This fixes the following errors:
fs/btrfs/reada.c: In function ‘btrfs_reada_wait’:
fs/btrfs/reada.c:958:42: error: invalid operands to binary < (have ‘atomic_t’
and ‘int’)
fs/btrfs/reada.c:961:41: error: invalid operands to binary < (have ‘atomic_t’
and ‘int’)
Signed-off-by: V
This fixes the following errors:
fs/btrfs/reada.c: In function ‘btrfs_reada_wait’:
fs/btrfs/reada.c:958:42: error: invalid operands to binary < (have ‘atomic_t’
and ‘int’)
fs/btrfs/reada.c:961:41: error: invalid operands to binary < (have ‘atomic_t’
and ‘int’)
Signed-off-by: V
On Tue, Jan 31, 2012 at 00:13, Mitch Harder
wrote:
> Jeff Mahoney has been working on a large overhaul of error
> handling/BUG_ONs. It is difficult to say when it will be ready, or
> if it will even address this specific problem.
>
> I'd go ahead and return the disk. I doubt you'll be the last
On Wed, Jan 25, 2012 at 20:03, Mitch Harder
wrote:
> A user has encountered a NULL pointer kernel oops in btrfs when
> encountering media errors. The problem has been identified
> as an unhandled NULL pointer returned from find_get_page().
> This modification simply checks for a NULL page, and re
On Wed, Jan 25, 2012 at 04:30, Mitch Harder
wrote:
>
> On Tue, Jan 24, 2012 at 10:24 AM, Vincent Vanackere
> wrote:
> > On 01/20/2012 09:54 PM, Mitch Harder wrote:
> >>
> >> On Fri, Jan 20, 2012 at 10:48 AM, Vincent Vanackere
> >> wrote:
> >>
On 01/20/2012 09:54 PM, Mitch Harder wrote:
On Fri, Jan 20, 2012 at 10:48 AM, Vincent Vanackere
wrote:
On 01/19/2012 05:24 PM, Mitch Harder wrote:
On Thu, Jan 19, 2012 at 8:42 AM, Vincent Vanackere
wrote:
Hi,
With the most current git kernel
(90a4c0f51e8e44111a926be6f4c87af3938a79c3
On 01/19/2012 05:24 PM, Mitch Harder wrote:
On Thu, Jan 19, 2012 at 8:42 AM, Vincent Vanackere
wrote:
Hi,
With the most current git kernel (90a4c0f51e8e44111a926be6f4c87af3938a79c3)
I'm still getting the same reproducible kernel panic when trying to read a
particular file stored on a
"software" part of this to be fixed - btrfs should
definitely not oops even in case of media error - before sending the
disk to RMA. Is there anything I can do to make progress on this ?
Regards,
Vincent
ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x
this bug... Who will trust a
filesystem that OOPs on media failure ? ;-)
Vincent
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
error... Is there any procedure I can follow / patch I could apply to
salvage my data while ignoring media errors ?
logs/OOPS at the end of this mail, please let me know if more
information is needed,
Best regards,
Vincent
media
error... Is there any procedure I can follow / patch I could apply to
salvage my data while ignoring media errors ?
logs/OOPS at the end of this mail, please let me know if more
information is needed,
Best regards,
Vincent
50 matches
Mail list logo
