Sulla posted on Wed, 01 Jan 2014 20:08:21 + as excerpted:
> Dear Duncan!
>
> Thanks very much for your exhaustive answer.
>
> Hm, I also thought of fragmentation. Alhtough I don't think this is
> really very likely, as my server doesn't serve things that likely cause
> fragmentation.
> It is
Austin S Hemmelgarn posted on Wed, 01 Jan 2014 15:12:40 -0500 as
excerpted:
> On 12/30/2013 11:02 AM, Austin S Hemmelgarn wrote:
>>
>> As an alternative to using bcache, you might try something simmilar to
>> the following:
>> 64G SSD with /boot, /, and /usr Other HDD with /var, /usr/portage,
Am 31.12.2013 12:46, schrieb Sulla:
Dear all!
On my Ubuntu Server 13.10 I use a RAID5 blockdevice consisting of 3 WD20EARS
drives. On this I built a LVM and in this LVM I use quite normal partitions
/, /home, SWAP (/boot resides on a RAID1.) and also a custom /data
partition. Everything (except
Leonidas Spyropoulos wrote (ao):
> Will this help with apt-get performance over btrfs file system? As far
> as I understand it it's happening because of multiple fsync calls.
apt-get install eatmydata
"This package contains a small LD_PRELOAD library (libeatmydata) and a
couple of helper utilitie
On 2014-01-02 03:49, Duncan wrote:
> Austin S Hemmelgarn posted on Wed, 01 Jan 2014 15:12:40 -0500 as
> excerpted:
>
>> On 12/30/2013 11:02 AM, Austin S Hemmelgarn wrote:
>>>
>>> As an alternative to using bcache, you might try something simmilar to
>>> the following:
>>> 64G SSD with /boot, /
Hello, I am trying to test your patches and they do not apply to latest
3.12 source or 3.13 git. Am I doing something wrong?
---logs for 3.12---
Hunk #1 succeeded at 59 with fuzz 2 (offset 1 line).
patching file init/Kconfig
Hunk #1 succeeded at 1085 (offset 96 lines).
Hunk #2 succeeded at 1096
Sorry for the spam, i just mixed up the order of your patches. they now
apply cleanly to 3.13 git.
Thanks
On 2/1/2014 4:32 μμ, Konstantinos Skarlatos wrote:
Hello, I am trying to test your patches and they do not apply to
latest 3.12 source or 3.13 git. Am I doing something wrong?
---logs for
On Wed, Jan 01, 2014 at 05:22:18PM +0100, Michal Nazarewicz wrote:
> > On Wed, Jan 1, 2014 at 5:19 AM, Michal Nazarewicz wrote:
> >> [commit 8185554d: fix incorrect inode acl reset] introduced a dead
> >> code by adding a condition which can never be true to an else
> >> branch. The condition can
On Thu, Dec 26, 2013 at 02:45:10PM +0800, Qu Wenruo wrote:
> 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)
Ok for adding the mount option.
> Reported-
On Mon, Dec 23, 2013 at 10:16:15PM -0800, Nacho Man wrote:
>
>
> On Monday, December 23, 2013 4:39 AM, Hugo Mills wrote:
>
> On Sun, Dec 22, 2013 at 10:27:17PM -0800, Nacho Man wrote:
> > Hello,
> > I ran dmesg and saw a bunch of these:
> > [564421.874063] BTRFS debug (device sda2): unlinked 32
On Mon, Dec 23, 2013 at 10:16:33AM -0700, Chris Murphy wrote:
>
> On Dec 22, 2013, at 11:27 PM, Nacho Man wrote:
>
> > Hello,
> > I ran dmesg and saw a bunch of these:
> > [564421.874063] BTRFS debug (device sda2): unlinked 32 orphans
>
> I sometimes see a similar message (minus debug and devic
On Jan 1, 2014, at 3:35 PM, Oliver Mangold wrote:
> On 01.01.2014 22:58, Chris Murphy wrote:
>> On Jan 1, 2014, at 2:27 PM, Oliver Mangold wrote:
>>
>>> I fear, I broke my FS by running btrfsck. I tried 'btrfsck --repair' and it
>>> fixed several problems but finally crashed with some debug m
On Thu, Dec 26, 2013 at 01:07:05PM +0800, Miao Xie wrote:
> +#define BTRFS_DELAYED_NODE_IN_LIST 0
> +#define BTRFS_DELAYED_NODE_INODE_DIRTY 1
> +
> struct btrfs_delayed_node {
> u64 inode_id;
> u64 bytes_reserved;
> @@ -65,8 +68,7 @@ struct btrfs_delayed_node {
> struct b
I am a bit confused and I have probably managed to outsmart myself.
For about 15 months, I have been running my system on a single, large
btrfs volume. It is RAID-0 on two SATA-III HDD's for a total of 1.9
TB. This is a home system running Siduction (Debian Sid) Linux. While
I have root, home, and
Austin S Hemmelgarn posted on Thu, 02 Jan 2014 07:36:06 -0500 as
excerpted:
> I think the triple seek+write is probably the biggest offender in my
> case, although COW and autodefrag probably don't help either. I'm kind
> of hesitant to put stuff that gets changed daily on a SSD, so I've ended
>
On Jan 2, 2014, at 3:28 PM, Tim Cuthbertson wrote:
>
> Am am at a point where I would like to do a fresh install of my OS
> without losing my home and data contents. And I do not think separate
> btrfs subvolumes will help me on that. Is that correct? Is there a way
> to prevent an OS installati
Tim Cuthbertson posted on Thu, 02 Jan 2014 16:28:33 -0600 as excerpted:
> I am a bit confused and I have probably managed to outsmart myself. For
> about 15 months, I have been running my system on a single, large btrfs
> volume. It is RAID-0 on two SATA-III HDD's for a total of 1.9 TB. This
> is
Conversion from ext4 works really well and is an important step for
adoption. After recently converting a large-ish device I noticed
dodgy performance, even after defragment & rebalance; noticeably
different from the quite good performance of a newly-created btrfs
with 16k leaf size, as is the def
On Thu, 2 Jan 2014 16:41:03 +0100, David Sterba wrote:
On Thu, Dec 26, 2013 at 02:45:10PM +0800, Qu Wenruo wrote:
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 aw
Tim Cuthbertson schrieb:
> I am a bit confused and I have probably managed to outsmart myself.
> For about 15 months, I have been running my system on a single, large
> btrfs volume. It is RAID-0 on two SATA-III HDD's for a total of 1.9
> TB. This is a home system running Siduction (Debian Sid) L
On Fri, 3 Jan 2014, Tim Cuthbertson wrote:
> I am a bit confused and I have probably managed to outsmart myself.
> For about 15 months, I have been running my system on a single, large
> btrfs volume. It is RAID-0 on two SATA-III HDD's for a total of 1.9
> TB. This is a home system running Siducti
Duncan <1i5t5.dun...@cox.net> schrieb:
> But because a full balance rewrites everything anyway, it'll effectively
> defrag too.
Is that really true? I thought it just rewrites each distinct extent and
shuffels chunks around... This would mean it does not merge extents
together.
Regards,
Kai
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This occurs sporadically and the machine is somewhat useless as a result
since most filesystem operations then hang. For example even reboot
fails because it does filesystem operations.
kernel is regular kernel.org 3.12.6 compiled with Ubuntu's kern
Some options should be paired to support triggering different functions
when remounting.
This patchset add these missing pairing mount options.
changelog:
v1: Initial commit with only barrier option
v2: Add other missing pairing options
Qu Wenruo (11):
btrfs: Add "barrier" option to support "-
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
Btrfs has autodefrag mount option but no pairing noautodefrag option,
which makes it impossible to disable autodefrag without umount.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add noauitodefrag mount option
---
Documentation/filesystems/btrfs.txt | 8 +---
fs/btrfs/super.c
Add noenospc_debug mount option to disable ENOSPC debug with
remount option.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add noenospc_debug mount option.
---
Documentation/filesystems/btrfs.txt | 3 ++-
fs/btrfs/super.c| 6 +-
2 files changed, 7 insertions(+), 2 deletions
Add datasum mount option to enable checksum with
remount option.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add datasum mount option.
---
Documentation/filesystems/btrfs.txt | 4 +++-
fs/btrfs/super.c| 11 ++-
2 files changed, 13 insertions(+), 2 deletions(-)
diff
Add noflushoncommit mount option to disable flush on commit with
remount option.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add noflushoncommit mount option.
---
Documentation/filesystems/btrfs.txt | 1 +
fs/btrfs/super.c| 8 +++-
2 files changed, 8 insertions(+), 1 dele
Add nodiscard mount option to disable discard with remount option.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add nodiscard mount option.
---
Documentation/filesystems/btrfs.txt | 7 +--
fs/btrfs/super.c| 5 +
2 files changed, 10 insertions(+), 2 deletions(-)
diff -
Add treelog mount option to enable tree log with
remount option.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add treelog mount option.
---
Documentation/filesystems/btrfs.txt | 3 ++-
fs/btrfs/super.c| 8 +++-
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a
Add nocheck_int mount option to disable integrity check with
remount option.
Signed-off-by: Qu Wenruo
---
changelog:
v2: add nocheck_int mount option
---
Documentation/filesystems/btrfs.txt | 3 +++
fs/btrfs/super.c| 15 ++-
2 files changed, 17 insertions(+), 1 d
Add acl mount option to enable acl with remount option.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add acl mount option.
---
Documentation/filesystems/btrfs.txt | 3 ++-
fs/btrfs/super.c| 6 +-
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/Documentation/
Add datacow mount option to enable copy-on-write with
remount option.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add datacow mount option.
---
Documentation/filesystems/btrfs.txt | 5 +++--
fs/btrfs/super.c| 8 +++-
2 files changed, 10 insertions(+), 3 deletions(-)
diff
Add noinode_cache mount option to disable inode map cache with
remount option.
Signed-off-by: Qu Wenruo
---
changelog:
v2: Add noinode_cache mount option.
---
Documentation/filesystems/btrfs.txt | 6 --
fs/btrfs/super.c| 7 +++
2 files changed, 11 insertions(+), 2 del
35 matches
Mail list logo
