17.01.2021 21:49, Anders Halman пишет:
> Hello,
>
> I try to backup my laptop over an unreliable slow internet connection to
> a even slower Raspberry Pi.
>
> To bootstrap the backup I used the following:
>
> # local
> btrfs send root.send.ro | pigz | split --verbose -d -b 1G
> rsync -aHAXxv --n
I wish there are btrfs unmount logs or ctree-close logs so that we can
know if the device was closed during the suspend. Those patches aren't
merged yet.
So here if I guess it correctly, the suspend does not seems to unmount
the filesystem, which means the device open is never closed. And, i
Hi Goffredo,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on kdave/for-next]
[also build test WARNING on v5.11-rc3 next-20210115]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as doc
On Sun, Jan 17, 2021 at 2:07 PM Damian Höster wrote:
>
> The nodatacow mount option seems to have no effect when mounting a
> subvolume into the same filesystem.
>
> I did some testing:
>
> sudo mount -o compress=zstd /dev/sda /mnt -> compression enabled
> sudo mount -o compress=zstd,nodatacow /de
Dear Zygo,
Thank you for this fantastic message. I hope you -- and the rest of the
list -- doesn't mind my jumping in mid-message...
On 17/01/2021 19:55, Zygo Blaxell wrote:
You can use a NVME device as a dm-cache or bcache device--the low-latency
interface is ideal for caching use cases, if
On Sat, Jan 16, 2021 at 04:27:29PM +0100, wrote:
>
> --- Ursprüngliche Nachricht ---
> Von: Zygo Blaxell
> Datum: 16.01.2021 02:04:38
> An: Andrea Gelmini
> Betreff: Re: Re: Raid1 of a slow hdd and a fast(er) SSD, howto to prioritize
> the SSD?
>
> This tells me everything I need to know ab
On 2021/1/18 上午7:38, chainofflowers wrote:
Hi all,
Hi Qu,
I am also getting this very same error on my system.
Actually, I am experiencing this since the following old bug was introduced AND
also even after it has been fixed:
https://lore.kernel.org/linux-btrfs/20190521190023.GA68070@glet/T/
Hi all,
Hi Qu,
I am also getting this very same error on my system.
Actually, I am experiencing this since the following old bug was introduced AND
also even after it has been fixed:
https://lore.kernel.org/linux-btrfs/20190521190023.GA68070@glet/T/
That (dm-related) bug was claimed to have been
On Sun, Jan 17, 2021 at 11:51 AM Anders Halman wrote:
>
> Hello,
>
> I try to backup my laptop over an unreliable slow internet connection to
> a even slower Raspberry Pi.
>
> To bootstrap the backup I used the following:
>
> # local
> btrfs send root.send.ro | pigz | split --verbose -d -b 1G
> rs
The nodatacow mount option seems to have no effect when mounting a
subvolume into the same filesystem.
I did some testing:
sudo mount -o compress=zstd /dev/sda /mnt -> compression enabled
sudo mount -o compress=zstd,nodatacow /dev/sda /mnt -> compression disabled
sudo mount -o nodatacow,compres
On Sat, Jan 16, 2021 at 11:42:03PM +, Graham Cobb wrote:
> I am about to deploy my first btrfs filesystems on NVME. Does anyone
> have any hints or advice? Initially they will be root disks, but I am
> thinking about also moving home disks and other frequently used data to
> NVME, but probably
On Sun, Jan 17, 2021 at 10:49:26AM -0800, Anders Halman wrote:
> Hello,
>
> I try to backup my laptop over an unreliable slow internet connection to a
> even slower Raspberry Pi.
>
> To bootstrap the backup I used the following:
>
> # local
> btrfs send root.send.ro | pigz | split --verbose -d -
I've moved a drive to a different sata controller during a suspend. Btrfs does
not understand that. I had to give the filesystem a new uuid before I could
access it again. Is there some setting in the kernel so it can deal with this?
Initial mounting of the btrfs partition:
[199167.697831] BTR
From: Goffredo Baroncelli
When this mode is enabled, the chunk allocation policy is modified
giving a different precedence between the disks depending by the chunk type.
A disk may be marked with the preferred_metadata flag to have higher chance
to host metadata.
There are 4 modes:
- preferred_m
From: Goffredo Baroncelli
---
fs/btrfs/ioctl.c | 67 ++
fs/btrfs/volumes.c | 2 +-
fs/btrfs/volumes.h | 2 ++
include/uapi/linux/btrfs.h | 40 +++
4 files changed, 110 insertions(+), 1 deletion(-)
diff --git a/f
Hi all,
This is an RFC; I wrote this patch because I find the idea interesting
even though it adds more complication to the chunk allocator.
The basic idea is to store the metadata chunk in the fasters disks.
The fasters disk are marked by the "preferred_metadata" flag.
BTRFS when allocate a n
From: Goffredo Baroncelli
---
fs/btrfs/sysfs.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/fs/btrfs/sysfs.c b/fs/btrfs/sysfs.c
index 19b9fffa2c9c..594e8445fe21 100644
--- a/fs/btrfs/sysfs.c
+++ b/fs/btrfs/sysfs.c
@@ -1416,11 +1416,22 @@ static ssize_t btrfs_devinfo_writeable
From: Goffredo Baroncelli
Add preferred_metadata mount option. This option accept the following values:
- disabled (default): the disk preferred metadata flag is ignored
- soft:the disk preferred metadata flag is a suggestion
on which disk the system may u
From: Goffredo Baroncelli
---
include/uapi/linux/btrfs_tree.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/uapi/linux/btrfs_tree.h b/include/uapi/linux/btrfs_tree.h
index 58d7cff9afb1..701ad550d596 100644
--- a/include/uapi/linux/btrfs_tree.h
+++ b/include/uapi/linux/btrfs_tree
Hello,
I try to backup my laptop over an unreliable slow internet connection to
a even slower Raspberry Pi.
To bootstrap the backup I used the following:
# local
btrfs send root.send.ro | pigz | split --verbose -d -b 1G
rsync -aHAXxv --numeric-ids --partial --progress -e "ssh -T -o
Compressi
On Tue, Jan 12, 2021 at 01:17:47PM -0800, Boris Burkov wrote:
> I recently changed clear_cache to not appear in mount options, as it has
> one shot semantics, which was breaking this test. Test explicitly that
> it _doesn't_ appear, which properly fails on old filesystems and passes
> on misc-next.
21 matches
Mail list logo
