On Fri, Jan 03, 2014 at 05:14:56PM -0700, Chris Murphy wrote:
>
> On Jan 3, 2014, at 5:33 AM, Marc MERLIN wrote:
> >
> > Would it be possible for whoever maintains btrfs-tools to change both
> > the man page and the help included in the tool to clearly state that
> > running the fsck tool is unl
On Fri, Jan 03, 2014 at 09:34:10PM +, Duncan wrote:
> > Thank you for that tip, I had been unaware of it 'till now.
> > This will make my virtualbox image directory much happier :)
>
> I think I said it, but it bears repeating. Once you set that attribute
> on the dir, you may want to move t
On Sat, 4 Jan 2014 02:56:39 PM Chris Mason wrote:
> Seconded +ADs-) We're really focused on nailing down these problems instead
> of hiding behind the experimental flag. I know we won't be perfect
> overnight, but it's time to focus on production workloads.
Perhaps an option here is to remove t
Jim Salter posted on Sat, 04 Jan 2014 16:22:53 -0500 as excerpted:
> On 01/04/2014 01:10 AM, Duncan wrote:
>> The example given in the OP was of a 4-device raid10, already the
>> minimum number to work undegraded, with one device dropped out, to
>> below the minimum required number to mount undeg
Chris Samuel posted on Sun, 05 Jan 2014 20:20:26 +1100 as excerpted:
> On Sat, 4 Jan 2014 02:56:39 PM Chris Mason wrote:
>
>> Seconded +ADs-) We're really focused on nailing down these problems
>> instead of hiding behind the experimental flag. I know we won't be
>> perfect overnight, but it's
Hello,
What messages in dmesg so you get when you use recovery?
I'll find out, tomorrow (I can't access the disk just now).
Here it is:
[90098.989872] btrfs: device fsid 989306aa-d291-4752-8477-0baf94f8c42f
devid 2 transid 162460 /dev/sdc1
That's all. The same in the syslog.
Do you have
Hello,
I replaced a failed 500G disk in btrfs raid1 with 2 smaller ones - 200
and 250GB. I started "btrfs device delete missing" command, which is
running since friday, and it still seems far from finished.
It seems to be doing something very strange: used space on the largest
drive is going d
Fengguang,
Instead of rebooting, can you trigger a crash dump when this happens
and send us the backtrace (to start with)?
Kent,
Did you do any btrfs test with your changes?
Regards,
Muthu
On Sun, Jan 5, 2014 at 1:46 AM, Fengguang Wu wrote:
> Hi Muthu,
>
> On Fri, Jan 03, 2014 at 11:51:31AM -08
On Jan 4, 2014, at 2:21 PM, Hendrik Friedel wrote:
> Hi Chris,
>
>
> >> I ran btrfsck on my volume with the repair option. When I re-run it, >>I
> >> get the same errors as before.
>>
>> Did you try mounting with -o recovery first?
>> https://btrfs.wiki.kernel.org/index.php/Problem_FAQ
>
>
On Jan 4, 2014, at 11:39 PM, Marc MERLIN wrote:
>
> Nope, I never posted anything until now. Hopefully you agree that it's
> not ok for btrfs/kernel to just kill my system for over 2H until I power
> it off before of defragging one file. I did hit a severe performance but
> if it's not a never
On 05.01.2014 18:43, Justus Seifert wrote:
> On 05.01.2014 05:34, dhan.war wrote:
>> hi all
>>
>> i am using up to date debian sid with xfce desktop environment. i am
>> using Linux 3.13-rc6-amd64 #1 SMP Debian 3.13~rc6-1~exp1 (2013-12-30)
>> x86_64 GNU/Linux from experimental.
>> i have installed
On 05.01.2014 05:34, dhan.war wrote:
> hi all
>
> i am using up to date debian sid with xfce desktop environment. i am
> using Linux 3.13-rc6-amd64 #1 SMP Debian 3.13~rc6-1~exp1 (2013-12-30)
> x86_64 GNU/Linux from experimental.
> i have installed usbmount to auto mount all the devices connected
>
On 01/05/2014 12:09 PM, Chris Murphy wrote:
I haven't read anything so far indicating defrag applies to the VM
container use case, rather nodatacow via xattr +C is the way to go. At
least for now.
Can you elaborate on the rationale behind database or VM binaries being
set nodatacow? I exper
On 01/05/2014 12:50 PM, Justus Seifert wrote:
oh i forgot: if you want to mount it without su privileges you have to
use:
/dev/sdc /path/to/your/favorite/mountpoint compress,noauto,users,user 0 0
If you want LZO compression, as you specified:
/dev/sdc /path/to/mountpoint compress=l
On 01/05/2014 01:02 PM, Jim Salter wrote:
If you want LZO compression, as you specified:
/dev/sdc /path/to/mountpoint compress=lzo,noauto,users,user 0 0
Better yet, if your btrfs is actually on /dev/sdc right now, let's get
that fstab entry mounting it by UUID instead.
ls
The structure for BTRFS_SET_RECEIVED_IOCTL packs differently on 32-bit
and 64-bit systems. This means that it is impossible to use btrfs
receive on a system with a 64-bit kernel and 32-bit userspace, because
the structure size (and hence the ioctl number) is different.
This patch adds a compatibil
On Sun, Jan 05, 2014 at 05:55:27PM +, Hugo Mills wrote:
> The structure for BTRFS_SET_RECEIVED_IOCTL packs differently on 32-bit
> and 64-bit systems. This means that it is impossible to use btrfs
> receive on a system with a 64-bit kernel and 32-bit userspace, because
> the structure size (and
Hello,
> distribution, used space on each device should be accordingly: 160,
> 216, and 405.
The last number should be 376, I copied the wrong one. Anyway, I deleted
as much data as possible, which probably won't help in the end, but at
the moment it's still going. Meanwhile, I made a script to
Jim Salter posted on Sun, 05 Jan 2014 12:54:44 -0500 as excerpted:
> On 01/05/2014 12:09 PM, Chris Murphy wrote:
>> I haven't read anything so far indicating defrag applies to the VM
>> container use case, rather nodatacow via xattr +C is the way to go. At
>> least for now.
Well, NOCOW from the
On Jan 4, 2014, at 2:16 PM, Jim Salter wrote:
>
> On 01/04/2014 02:18 PM, Chris Murphy wrote:
>> I'm not sure what else you're referring to?(working on boot environment of
>> btrfs)
>
> Just the string of caveats regarding mounting at boot time - needing to
> monkeypatch 00_header to avoid t
On Dec 31, 2013, at 4:46 AM, Sulla wrote:
> Dear all!
>
> On my Ubuntu Server 13.10 I use a RAID5 blockdevice consisting of 3 WD20EARS
Sulla is this md raid5? If so can you report the result from mdadm -D
, I'm curious what the chunk size is. Thanks.
Chris Murphy--
To unsubscribe from this l
On Jan 5, 2014, at 12:57 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>
> But I do very little snapshotting here, and as a result hadn't considered
> the knockon effect of 100K-plus extents in perhaps 1000 snapshots.
I wonder if this is an issue with snapshot aware defrag? Some problems were
fixe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Chris!
Certainly: I have 3 HDDs, all of which WD20EARS. Originally I wanted to
let btrfs handle all 3 devices directly without making partitions, but
this was impossible, as at least /boot needed to be ext4, at least back
then when I set up the s
On Sun, 05 Jan 2014 08:42:46 -0500
Jim Salter wrote:
> On Jan 5, 2014 1:39 AM, Marc MERLIN wrote:
> >
> > On Fri, Jan 03, 2014 at 09:34:10PM +, Duncan wrote:
> > Yes, I got that. That why I ran btrfs defrag on the files after that
>
> Why are you trying to defrag an SSD? There's no seek pe
On 2014/01/05 11:17 PM, Sulla wrote:
Certainly: I have 3 HDDs, all of which WD20EARS.
Maybe/maybe-not off-topic:
Poor hardware performance, though not necessarily the root cause, can be
a major factor with these errors.
WD Greens (Reds too, for that matter) have poor non-sequential
performan
Hello,
I am currently playing with snapshots and manual deduplication of
files. During these tests I noticed the change of ctime and mtime in
the snapshot after the deduplication with FILE_EXTENT_SAME. Does this
happens on purpose? Otherwise I would like to have ctime and mtime
left unmodified, be
On Mon, 06 Jan 2014 00:36:22 +0200
Brendan Hide wrote:
> I had 8x 1.5TB WD1500EARS drives in an mdRAID5 array. With it I had a
> single 250GB IDE disk for the OS. When the very old IDE disk inevitably
> died, I decided to use a spare 1.5TB drive for the OS. Performance was
> bad enough that I
On Jan 5, 2014, at 2:17 PM, Sulla wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear Chris!
>
> Certainly: I have 3 HDDs, all of which WD20EARS.
These drives don't have a configurable SCT ERC, so you need to modify the SCSI
block layer timeout:
echo 120 >/sys/block/sdX/device
On Jan 5, 2014, at 4:48 PM, Chris Murphy wrote:
>
> On Jan 5, 2014, at 2:17 PM, Sulla wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Dear Chris!
>>
>> Certainly: I have 3 HDDs, all of which WD20EARS.
>
> These drives don't have a configurable SCT ERC, so you need to mod
On Jan 5, 2014, at 3:36 PM, Brendan Hide wrote:
> WD Greens (Reds too, for that matter) have poor non-sequential performance.
> An educated guess I'd say there's a 15% chance this is a major factor to the
> problem and, perhaps, a 60% chance it is merely a "small contributor" to the
> problem
On Jan 5, 2014, at 5:15 PM, Chris Murphy wrote:
>
> On Jan 5, 2014, at 3:36 PM, Brendan Hide wrote:
>
>> WD Greens (Reds too, for that matter) have poor non-sequential performance.
>> An educated guess I'd say there's a 15% chance this is a major factor to the
>> problem and, perhaps, a 60%
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks Chris!
Thanks for your support.
>> echo 120 >/sys/block/sdX/device/timeout
timeout is 30 for my HDDs. I'm well aware that the WD green HDDs are not
the perfect ones for servers, but they were cheaper - and quieter - than
the black ones for ser
On Jan 5, 2014, at 5:25 PM, Sulla wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Thanks Chris!
>
> Thanks for your support.
>
>>> echo 120 >/sys/block/sdX/device/timeout
> timeout is 30 for my HDDs.
I don't think those drives support a configurable time out; the Green hasn't
s
On fri, 3 Jan 2014 18:52:44 +0100, David Sterba wrote:
On Fri, Jan 03, 2014 at 02:10:30PM +0800, Qu Wenruo wrote:
Add noinode_cache mount option to disable inode map cache with
remount option.
This looks almost safe, there's a sync_filesystem called before the
filesystem's remount handler, the
On fri, 03 Jan 2014 11:52:07 -0600, Eric Sandeen wrote:
On 1/3/14, 12:10 AM, Qu Wenruo wrote:
Some options should be paired to support triggering different functions
when remounting.
This patchset add these missing pairing mount options.
I think this really would benefit from a regression test
On fri, 3 Jan 2014 18:58:28 +0100, David Sterba wrote:
On Fri, Jan 03, 2014 at 02:10:23PM +0800, Qu Wenruo wrote:
Some options should be paired to support triggering different functions
when remounting.
This patchset add these missing pairing mount options.
Thanks!
btrfs: Add nocheck_int m
On Fri, 3 Jan 2014 18:13:08 +0100, David Sterba wrote:
On Fri, Jan 03, 2014 at 02:10:26PM +0800, Qu Wenruo wrote:
Add nocheck_int mount option to disable integrity check with
remount option.
+ nocheck_int disables all the debug options above.
I think this option is not needed, the integr
On Jan 5, 2014, at 6:29 PM, Sulla wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Chris!
>
> # sudo smartctl -l scterc /dev/sda
> tells me
> SCT Error Recovery Control command not supported
>
> you're right. the /sys/block/sdX/device/timeout file probably is useless then.
OK
Some options should be paired to support triggering different functions
when remounting.
This patchset add these missing pairing mount options except noinode_cache,
which may need more investigation to ensure the safety and will be sent as
independent patch.
Qu Wenruo (9):
btrfs: Add "barrier"
Btrfs can be remounted without barrier, but there is no "barrier" option
so nobody can remount btrfs back with barrier on. Only umount and
mount again can re-enable barrier.(Quite awkward)
Also the mount options in the document is also changed slightly for the
further pairing options changes.
Rep
Add noflushoncommit mount option to disable flush on commit with
remount option.
Signed-off-by: Qu Wenruo
Reviewed-by: David Sterba
---
Changelog:
v2: Add noflushoncommit option
v3: None
---
Documentation/filesystems/btrfs.txt | 1 +
fs/btrfs/super.c| 8 +++-
2 files ch
Add noenospc_debug mount option to disable ENOSPC debug with
remount option.
Signed-off-by: Qu Wenruo
Reviewed-by: David Sterba
---
Changelog:
v2: Add noenospc_debug option
v3: None
---
Documentation/filesystems/btrfs.txt | 3 ++-
fs/btrfs/super.c| 5 +
2 files changed,
Btrfs has autodefrag mount option but no pairing noautodefrag option,
which makes it impossible to disable autodefrag without umount.
Signed-off-by: Qu Wenruo
Reviewed-by: David Sterba
---
Changelog:
v2: Add noautodefrag option
v3: None
---
Documentation/filesystems/btrfs.txt | 8 +---
fs/
Add nodiscard mount option to disable discard with remount option.
Signed-off-by: Qu Wenruo
Reviewed-by: David Sterba
---
Changelog:
v2: Add nodiscard option
v3: None
---
Documentation/filesystems/btrfs.txt | 7 +--
fs/btrfs/super.c| 6 +-
2 files changed, 10 insert
Add datacow mount option to enable copy-on-write with
remount option.
Signed-off-by: Qu Wenruo
Reviewed-by: David Sterba
---
Changelog:
v2: add datacow mount option
v3: None
---
Documentation/filesystems/btrfs.txt | 5 +++--
fs/btrfs/super.c| 8 +++-
2 files changed, 10
Add datasum mount option to enable checksum with
remount option.
Signed-off-by: Qu Wenruo
Reviewed-by: David Sterba
---
Changelog:
v2: Add datasum option
v3: None
---
Documentation/filesystems/btrfs.txt | 4 +++-
fs/btrfs/super.c| 10 ++
2 files changed, 13 inserti
Add treelog mount option to enable tree log with
remount option.
Signed-off-by: Qu Wenruo
Reviewed-by: David Sterba
---
Changelog:
v2: Add treelog option
v3: None
---
Documentation/filesystems/btrfs.txt | 3 ++-
fs/btrfs/super.c| 8 +++-
2 files changed, 9 insertions(+)
Add acl mount option to enable acl with remount option.
Signed-off-by: Qu Wenruo
Reviewed-by: David Sterba
---
Changelog:
v2: add acl option
v3: None
---
Documentation/filesystems/btrfs.txt | 3 ++-
fs/btrfs/super.c| 6 +-
2 files changed, 7 insertions(+), 2 deletions(-
48 matches
Mail list logo
