Hi all,
I've replaced my notebook HDD with an SSHD hybrid disk (Seagate ST1000LM).
contrary to my experience with other similar machines, the disk
performance are really poor.
I suspect that it depends on btrfs detecting it as an SSD disk
(according to this dmesg message):
BTRFS: detected SSD de
On 06/10/2015 02:58 PM, Martin wrote:
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.
the failed(ing) dis
Hi all,
I've replaced my notebook HDD with an SSHD hybrid disk (Seagate ST1000LM).
contrary to my experience with other similar machines, the disk
performance are really poor.
I suspect that it depends on btrfs detecting it as an SSD disk
(according to this dmesg message):
BTRFS: detected SSD d
On Thu, Jun 04, 2015 at 11:31:07AM -0400, Mike Snitzer wrote:
> This patch _really_ concerns me because just in DM alone I found you
> took liberties that you shouldn't have and created a regression. First
> issue is a real bug (your proposed dm-io.c:dmio_complete change missed
> that dm-io uses e
On Wed, Jun 10, 2015 at 3:09 AM, Liu Bo wrote:
> 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
On Wed, Jun 10, 2015 at 12:50:54PM +1000, Neil Brown wrote:
> This introduces a use-after-free. put_buf(r1_bio) can result in bio_put on
> 'bio'.
> It is safe to move the put_buf call after the md_done_sync(), but it is
> probably best to leave the 'update' variable as it. i.e. Just change:
>
>
On Wed, Jun 10, 2015 at 9:47 AM, Qu Wenruo wrote:
> Hi,
>
> You can try nossd mount option (mount DEV MNT -o nossd), which will disable
> ssd related optimization.
thanks Qu!
I've tried it, but the disk still seems slow as hell.
> But according to my experience, even enable ssd mode on HDD, per
Hi Filipi,
2015-06-09 18:36 GMT+08:00 Filipe David Manana :
> 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 "d
On Thu, May 14, 2015 at 02:16:58PM +0200, Toralf Förster wrote:
> I created at a 3 TB btrfs formatted disk a btrfs subvolume, unpacked a
> minimal Gentoo Linux in it, created in addition few files within it under
> ./tmp and bind mount from the host few files onto those files. If I now
> delete
On Tue, May 26, 2015 at 12:55:42AM +0100, fdman...@kernel.org wrote:
> 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 sec
On Wed, Jun 10, 2015 at 11:41 AM, Liu Bo wrote:
> On Tue, May 26, 2015 at 12:55:42AM +0100, fdman...@kernel.org wrote:
>> 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.97
On Wed, Jun 10, 2015 at 11:44:17AM +0100, Filipe Manana wrote:
> On Wed, Jun 10, 2015 at 11:41 AM, Liu Bo wrote:
> > On Tue, May 26, 2015 at 12:55:42AM +0100, fdman...@kernel.org wrote:
> >> From: Filipe Manana
> >>
> >> Zygo Blaxell and other users have reported occasional hangs while an
> >> in
On Wed, Jun 10, 2015 at 12:05 PM, Liu Bo wrote:
> On Wed, Jun 10, 2015 at 11:44:17AM +0100, Filipe Manana wrote:
>> On Wed, Jun 10, 2015 at 11:41 AM, Liu Bo wrote:
>> > On Tue, May 26, 2015 at 12:55:42AM +0100, fdman...@kernel.org wrote:
>> >> From: Filipe Manana
>> >>
>> >> Zygo Blaxell and oth
From: Filipe Manana
We have a race between deleting an unused block group and balancing the
same block group that leads to an assertion failure/BUG(), producing the
following assertion failure/BUG_ON():
[181631.208236] BTRFS: assertion failed: 0, file: fs/btrfs/volumes.c, line: 2622
[181631.2205
On Wed, Jun 10, 2015 at 12:12:11PM +0100, Filipe Manana wrote:
> On Wed, Jun 10, 2015 at 12:05 PM, Liu Bo wrote:
> > On Wed, Jun 10, 2015 at 11:44:17AM +0100, Filipe Manana wrote:
> >> On Wed, Jun 10, 2015 at 11:41 AM, Liu Bo wrote:
> >> > On Tue, May 26, 2015 at 12:55:42AM +0100, fdman...@kernel
From: Zhao Lei
Because btrfs support scrub raid56 parity stripe now.
Signed-off-by: Zhao Lei
---
fs/btrfs/scrub.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/btrfs/scrub.c b/fs/btrfs/scrub.c
index a13f91a..5ee5630 100644
--- a/fs/btrfs/scrub.c
+++ b/fs/btrfs/scrub.c
On Wed, Jun 10, 2015 at 12:27 PM, Liu Bo wrote:
> On Wed, Jun 10, 2015 at 12:12:11PM +0100, Filipe Manana wrote:
>> On Wed, Jun 10, 2015 at 12:05 PM, Liu Bo wrote:
>> > On Wed, Jun 10, 2015 at 11:44:17AM +0100, Filipe Manana wrote:
>> >> On Wed, Jun 10, 2015 at 11:41 AM, Liu Bo wrote:
>> >> > On
From: Filipe Manana
The comment was not correct about the part where it says the endio
callback of the bio might have not yet been called - update it
to mention that by that time the endio callback execution might
still be in progress only.
Signed-off-by: Filipe Manana
---
fs/btrfs/inode.c | 5
Hello Anand,
the failed disk was removed. My procedure was the following:
- I found some write errors in the kernel log, so
- I shutdown the system
- I removed the failed disk
- I powered on the system
- I mounted the remaining disk degraded,rw (works OK)
- the system works an and was reboo
On Wed, Jun 10, 2015 at 9:26 AM, Filipe David Manana wrote:
> On Wed, Jun 10, 2015 at 3:09 AM, Liu Bo wrote:
>> 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 ti
On Wed, Jun 10, 2015 at 01:45:29PM +0100, Filipe David Manana wrote:
> On Wed, Jun 10, 2015 at 9:26 AM, Filipe David Manana
> wrote:
> > On Wed, Jun 10, 2015 at 3:09 AM, Liu Bo wrote:
> >> On Tue, Jun 09, 2015 at 01:56:41PM +0100, Filipe David Manana wrote:
> >>> On Tue, Jun 9, 2015 at 1:04 PM,
On Wed, Jun 10, 2015 at 12:51:15PM +0100, Filipe Manana wrote:
> On Wed, Jun 10, 2015 at 12:27 PM, Liu Bo wrote:
> > On Wed, Jun 10, 2015 at 12:12:11PM +0100, Filipe Manana wrote:
> >> On Wed, Jun 10, 2015 at 12:05 PM, Liu Bo wrote:
> >> > On Wed, Jun 10, 2015 at 11:44:17AM +0100, Filipe Manana w
On Wed, Jun 10, 2015 at 01:02:12PM +0100, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> The comment was not correct about the part where it says the endio
> callback of the bio might have not yet been called - update it
> to mention that by that time the endio callback execution might
> st
On Wed, Jun 10 2015 at 4:11am -0400,
Christoph Hellwig wrote:
> On Thu, Jun 04, 2015 at 11:31:07AM -0400, Mike Snitzer wrote:
> > This patch _really_ concerns me because just in DM alone I found you
> > took liberties that you shouldn't have and created a regression. First
> > issue is a real b
On Wed, Jun 10 2015 at 11:26am -0400,
Mike Snitzer wrote:
> On Wed, Jun 10 2015 at 4:11am -0400,
> Christoph Hellwig wrote:
>
> > On Thu, Jun 04, 2015 at 11:31:07AM -0400, Mike Snitzer wrote:
> > > This patch _really_ concerns me because just in DM alone I found you
> > > took liberties that y
On Wed, Jun 10, 2015 at 12:01:12PM -0400, Mike Snitzer wrote:
> > I'll queue a patch to rename 'error' to 'error_bits' where appropriate.
>
> See:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=f368f463e4cef696ad6b102dbaf5c10dfca7cc63
Can we wait
On Wed, Jun 10 2015 at 12:04pm -0400,
Christoph Hellwig wrote:
> On Wed, Jun 10, 2015 at 12:01:12PM -0400, Mike Snitzer wrote:
> > > I'll queue a patch to rename 'error' to 'error_bits' where appropriate.
> >
> > See:
> > https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/c
So Is it safe to use raid 6 with btrfs for home storage now? I will
have backup on ZFS.
On Wed, Jun 10, 2015 at 11:50 AM, Mike Snitzer wrote:
> On Wed, Jun 10 2015 at 12:04pm -0400,
> Christoph Hellwig wrote:
>
>> On Wed, Jun 10, 2015 at 12:01:12PM -0400, Mike Snitzer wrote:
>> > > I'll queue a
Kind of a big feature of btrfs is being able to have a default subvol. However
the receive code generates the paths to the subvols from the root of the fs,
even in the case of a default subvol. So instead figure out if we're inside of
a subvol, either because we have a different default or we've
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'
Hi,
Can this patch please be considered for upstream inclusion? I reviewed
it myself and have tested it on a few files with an updated duperemove
branch:
https://github.com/markfasheh/duperemove/tree/alignment_fix
as described below, this allows us to dedupe the tail extents of files
whose size
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/9/15 8:05 PM, Jeff Mahoney wrote:
> On 6/9/15 4:48 PM, Jeff Mahoney wrote:
>> On 6/8/15 10:12 AM, Filipe David Manana wrote:
>>> Running the following in a loop until it returns failure ($?
>>> != 0) triggers an apparent corruption issue most of t
On Tue, Jun 09, 2015 at 07:55:05PM +0200, pu...@xs4all.nl wrote:
> 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.
They created a subvolume called "@" and then put all the other
subvolumes
I see... quite underwhelming explanation :-) I thought there is some
special trick here.
Thanks,
Gábor
On Wed, 10 Jun 2015 23:10:14 +
Hugo Mills wrote:
> On Tue, Jun 09, 2015 at 07:55:05PM +0200, pu...@xs4all.nl wrote:
> > Hi,
> >
> > I've noticed this "@" sign in the subvolume's path w
> On 10 Jun 2015, at 5:35 pm, Martin wrote:
>
> Hello Anand,
>
> the failed disk was removed. My procedure was the following:
>
> - I found some write errors in the kernel log, so
> - I shutdown the system
> - I removed the failed disk
> - I powered on the system
> - I mounted the remaining d
Hello!, use arch linux with the latest kernel, i am trying to do raid
5 on 3 devices, but i get this on
btfs fi usage:
"WARNING: RAID56 detected, not implemented"
what is not implemented?
full output:
WARNING: RAID56 detected, not implemented
WARNING: RAID56 detected, not implemented
WARNING:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/10/15 7:10 PM, Hugo Mills wrote:
> On Tue, Jun 09, 2015 at 07:55:05PM +0200, pu...@xs4all.nl wrote:
>> 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
>
Hi, Omar Sandoval
I tested this patchset with my script, but see general protection fault
again.
NODE: kvm with virtio disk
ROOTFS: RHEL6 with btrfs-progs v4.0
KERNEL: v4.1-rc6 with 4 patchs in this patchset
Maybe my test have small different with yours,
but it seems is similar bug, could you che
Guilherme Gonçalves posted on Wed, 10 Jun 2015 21:05:38 -0300 as
excerpted:
> Hello!, use arch linux with the latest kernel, i am trying to do raid 5
> on 3 devices, but i get this on btfs fi usage:
>
> "WARNING: RAID56 detected, not implemented"
>
> what is not implemented?
That warning is pu
This does not look correct. Please check.
julia
On Thu, 11 Jun 2015, kbuild test robot wrote:
> TO: Liu Bo
> CC: "Chris Mason Chris Mason"
> CC: David Sterba
> CC: linux-btrfs@vger.kernel.org
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
> integration-4.2
On Thu, Jun 11, 2015 at 11:52:30AM +0800, Zhao Lei wrote:
> Hi, Omar Sandoval
>
> I tested this patchset with my script, but see general protection fault
> again.
> NODE: kvm with virtio disk
> ROOTFS: RHEL6 with btrfs-progs v4.0
> KERNEL: v4.1-rc6 with 4 patchs in this patchset
>
> Maybe my test
On Thu, Jun 11, 2015 at 08:07:09AM +0200, Julia Lawall wrote:
> This does not look correct. Please check.
Oops, thanks for pointing it out.
Sorry for my miss, here is the fix.
(Chris, if you prefer me to fold this into the original patch, I'll do
it.)
Thanks,
-liubo
>From de72ac1c6612441bd5e
On Thu, Jun 11, 2015 at 02:23:20PM +0800, Liu Bo wrote:
> On Thu, Jun 11, 2015 at 08:07:09AM +0200, Julia Lawall wrote:
> > This does not look correct. Please check.
>
> Oops, thanks for pointing it out.
>
> Sorry for my miss, here is the fix.
>
> (Chris, if you prefer me to fold this into the
43 matches
Mail list logo
