On 11/28/18 1:23 PM, Nikolay Borisov wrote:
On 28.11.18 г. 13:05 ч., Andrea Gelmini wrote:
Signed-off-by: Andrea Gelmini
---
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index bab2f1983c07..babbd75d91d2 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -104,7 +104,7 @@ stat
On 04/28/2018 04:05 AM, Qu Wenruo wrote:
On 2018年04月28日 01:41, Brendan Hide wrote:
Hey, all
I'm following up on the queries I had last week since I have installed
the NVMe SSD into the PCI-e adapter. I'm having difficulty knowing
whether or not I'm doing these benchmarks c
Hey, all
I'm following up on the queries I had last week since I have installed
the NVMe SSD into the PCI-e adapter. I'm having difficulty knowing
whether or not I'm doing these benchmarks correctly.
As a first test, I put together a 4.7GB .tar containing mostly
duplicated copies of the kern
Thank you, all
Though the info is useful, there's not a clear consensus on what I
should expect. For interest's sake, I'll post benchmarks from the device
itself when it arrives.
I'm expecting at least that I'll be blown away :)
On 04/18/2018 09:23 PM, Chris Murphy wrote:
On Wed, Apr 18,
Hi, all
I'm looking for some advice re compression with NVME. Compression helps
performance with a minor CPU hit - but is it still worth it with the far
higher throughputs offered by newer PCI and NVME-type SSDs?
I've ordered a PCIe-to-M.2 adapter along with a 1TB 960 Evo drive for my
home d
t I also don't want to have to tell
people they can't adopt it because a) they don't (or never will)
understand it; and b) they're going to resent me for their irresponsibly
losing their own data.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.
The title seems alarmist to me - and I suspect it is going to be
misconstrued. :-/
From the release notes at
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.4_Release_Notes/chap-Red_Hat_Enterprise_Linux-7.4_Release_Notes-Deprecated_Functionality.html
"Btrfs has
mplementation of *any* combination of these, whereas the idea was
simply to create a way to refer to the "raid" levels in a consistent way.
I hope this brings some clarity. :)
regards,
Jan Vales
--
I only read plaintext emails.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://w
els that neither dmcrypt or per-file encryption address. Only if
the generic code cannot be expanded to address specific threat
models should you then implement something that is unique to
btrfs
Agreed, this sounds like a far safer and achievable implementation process.
Cheers,
Dav
On 06/09/2016 03:07 PM, Austin S. Hemmelgarn wrote:
On 2016-06-09 08:34, Brendan Hide wrote:
Hey, all
I noticed this odd behaviour while migrating from a 1TB spindle to SSD
(in this case on a LUKS-encrypted 200GB partition) - and am curious if
this behaviour I've noted below is expect
y to remove a potentially failing disk
(common use case for dev delete), I'd much rather that btrfs does *not*
write data to the disk I'm trying to remove, making this a potentially
severe bug.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
-
won't necessarily answer all questions about allocation, I
strongly suggest checking out Hugo's btrfs calculator **
I hope this is helpful.
* http://comments.gmane.org/gmane.comp.file-systems.btrfs/34717 /
https://www.spinics.net/lists/linux-btrfs/msg33742.html
* http://comments.g
ill likely never bother with f2fs unless I
somehow end up working on a project requiring relatively small storage
in Flash (as that is what f2fs was designed for).
If someone can provide or link to some proper comparison data, that
would be nice. :)
--
__
Brendan Hide
http://
On 12/1/2015 12:05 PM, Brendan Hide wrote:
On 11/30/2015 11:09 PM, Chris Murphy wrote:
On Mon, Nov 30, 2015 at 1:37 PM, Austin S Hemmelgarn
wrote:
I've had multiple cases of disks that got one write error then were
fine for
more than a year before any further issues. My thought is a
sidered, and how many are allowed).
OK.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
alance/convert to a 3-disk raid5 is also important.
Please shoot down my concerns. :)
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to ma
in v2.
>
> Thanks for reviewing!
>
Late to the party. DUP *implies* single device but there are cases
where dup is used on a multi-device fs. Even if the use-cases aren't
good or intended to be long-term, they are still valid, right?
- --
__
Brendan Hide
http:
s root) and send us the output - then maybe
someone will be kind enough to point you in the right direction:
uname -a
cat /etc/*release
btrfs --version
btrfs fi show
cat /proc/mdstat
fdisk -l
gdisk -l
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015/02/09 10:30 PM, Kai Krakow wrote:
> Brendan Hide schrieb:
>
>> I have the following two lines in
>> /etc/udev/rules.d/61-persistent-storage.rules for two old 250GB
[snip]
> Wouldn't it be easier and more efficien
ynchronise my Arch desktop's
system journal to a couple of local and remote servers of mine. A much
cleaner way to do this would be to use an external syslog server - I
haven't yet looked into doing that properly, however.
http://swiftspirit.co.za/down/smart_scan
http://swiftspirit.co
office/home and the server is on another continent? Your session dies
and you lose 10 hours of work/waiting. With a screen session, that is no
longer true.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe l
, the chances of losing *some* data is already clearly shown to be
very close to 100%.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord.
Hey, guys
This is on my ArchLinux desktop. Current values as follows and the exact
error is currently reproducible. Let me know if you want me to run any
tests/etc. I've made an image (76MB) and can send the link to interested
parties.
I have come across this once before in the last few week
On 2014/12/02 09:31, Brendan Hide wrote:
On 2014/12/02 07:54, MegaBrutal wrote:
Hi all,
I know there is a btrfstune, but it doesn't provide all the
functionality I'm thinking of.
For ext2/3/4 file systems I can get a bunch of useful data with
"tune2fs -l". How can I retri
her equivalents, the same/similar answer applies. There
simply aren't a lot of tuneables available "right now".
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe li
t the obvious cost.
I can imagine some use-cases where you might even want more than one
algorithm to be used and stored. Not sure if that makes me a madman,
though. ;)
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: sen
- and David's suggestion (separate thread) would be able
to take advantage of that.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord..
ght have.
Personally, 3 seems pragmatic - but not necessarily "correct". :-/
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...
g empty chunks makes them available for re-allocation - so that
is directly useful and light on workload.
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
t
This
leaves the probable cause at:
- the drive itself
- the cable/ports
with a negligibly-possible cause at the motherboard chipset.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-b
rrectly. I interpret this as:
Options=defaults,nofail,subvol=archive-local/@system.@system.CURRENT
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of
hard disks in particular) having either bad
connectors, or bad strain-reliefs, and failing after only a few hundred hours
of use.
Thanks. I'll try this first. :)
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: se
On 2014/11/18 09:36, Roman Mamedov wrote:
On Tue, 18 Nov 2014 09:29:54 +0200
Brendan Hide wrote:
Hey, guys
See further below extracted output from a daily scrub showing csum
errors on sdb, part of a raid1 btrfs. Looking back, it has been getting
errors like this for a few days now.
The disk
Hey, guys
See further below extracted output from a daily scrub showing csum
errors on sdb, part of a raid1 btrfs. Looking back, it has been getting
errors like this for a few days now.
The disk is patently unreliable but smartctl's output implies there are
no issues. Is this somehow standar
uot;stupid but fixable". Again, we have similar
choices:
- give a clear warning and ignore bad disk(s)
- give a clear error and panic
2014-11-17 15:59 GMT+09:00 Brendan Hide :
cc'd bug-g...@gnu.org for FYI
On 2014/11/17 03:42, Duncan wrote:
MegaBrutal posted on Sun, 16 Nov 2014 22:35:
y have
something like this built-in that we're simply not utilising fully?
I'm not exactly sure of the "correct" way to fix b) except that I
imagine it would be trivial to fix once a) is fixed.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
On 2014/10/02 07:51, Brendan Hide wrote:
On 2014/10/02 01:31, Duncan wrote:
[snip]
I'm not sure if there is a mount option for this use case however. The
option descriptions for "nodatasum" and "nodatacow" imply that *new*
checksums are not generated. In this case th
atasum" and "nodatacow" imply that *new*
checksums are not generated. In this case the checksums already exist.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe li
o securely delete the metadata
referring to that file. That would satisfy the concept that there is no
evidence that the file ever existed in that location. The fact that it
actually does still legitimately exist elsewhere is not a caveat - it is
simply acting within standard behaviour.
--
____
ion steps, including the defrag, in
proper order.
I've inserted information specific to this in the wiki. Others with wiki
accounts, feel free to review:
https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3#Before_first_use
--
__
Brendan Hide
http://swiftspirit.co.za/
ht
body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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 <<= 10;
+ case 'P':
+ case 'p':
+ ret <<= 10;
+ case 'T':
+ case 't':
+ ret <<= 10;
case 'G':
case 'g':
ret <<= 10;
Ah, I se
ely to be fixed for a very
long time. Should we feel uncomfortable with the patch, as is, because
of language/correctness friction? Pedantry included, the patch is
correct. ;)
Thanks
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe fro
n one mean that we always need to mount with noatime or
read-only to allow snapshot defragging to do anything?
That is a very good question. I very rarely have mounts without noatime
- and usually only because I hadn't thought of it.
Regards,
Martin
--
__
Brendan
dev.
Thanks,
Qu
Thanks, Anand
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
ripling the size of *all* metadata.
It is a good idea. The next question to me is whether or not it is
something that can be implemented elegantly and whether or not a
talented *dev* thinks it is a good idea.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?A
of VERY little corruption. That is where the
peace-of-mind/bragging rights come in.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vge
are looking for. The last
traffic on the mailing list regarding that was in August last year. It
looks like it was pulled into the main kernel repository on September 1st.
The last commit to the duperemove application was on April 20th this
year. Maybe Mark (cc'd) can provi
underlying issue, but it will make it less of an issue for BTRFS.
More ideally, btrfs should dispatch them in parallel. This will likely
be looked into for N-way mirroring. Having 3 or more copies and working
in the current way would be far from optimal.
--
__
Brendan Hide
http:
- and that exporting to a
man page is simple. I can't vouch for it except to say that it is worth
investigating.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-b
ail checksum, without another reliable copy to fix it since that other
copy is in the weak area already.
Another alternative would be using something like mdraid's raid10 "far"
layout, with btrfs on top of that...
In the "copies= option" thread Brendan Hide st
t with a predictable UUID.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
nother new chunk.
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
will always be that the majority of chunks are going to be relatively
full, avoiding the pathological use-case.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the
Hi, Marc. Inline below. :)
On 2014/05/06 02:19 PM, Marc MERLIN wrote:
On Mon, May 05, 2014 at 07:07:29PM +0200, Brendan Hide wrote:
"In the case above, because the filesystem is only 55% full, I can
ask balance to rewrite all chunks that are more than 55% full:
legolas:~# btrfs balance
nge we have in this
area at the moment is ssd_spread, which doesn't do very much. It also
has the potential for really killing performance and/or file
fragmentation.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
On 05/05/14 19:07, Brendan Hide wrote:
On 05/05/14 14:16, Marc MERLIN wrote:
I've just written this new page:
http://marc.merlins.org/perso/btrfs/post_2014-05-04_Fixing-Btrfs-Filesystem-Full-Problems.html
First, are there problems in it?
Second, are there other FS full issues I s
to get through is if you can't balance
*because* of ENOSPC errors. I'd probably start scouring the mailing list
archives if I ever come across that.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line
On 05/05/14 07:50, Marc MERLIN wrote:
On Mon, May 05, 2014 at 06:11:28AM +0200, Brendan Hide wrote:
The "per-device" used amount refers to the amount of space that has
been allocated to chunks. That first one probably needs a balance.
Btrfs doesn't behave very well when availab
On 05/05/14 06:36, Roman Mamedov wrote:
On Mon, 05 May 2014 06:13:30 +0200
Brendan Hide wrote:
1) There will be a *very* small performance penalty (negligible, really)
Oh, really, it's slower to mount the device directly? Not that I really
care, but that's unexpected.
Um ... the
On 2014/05/05 02:56 AM, Marc MERLIN wrote:
On Sun, May 04, 2014 at 09:07:55AM +0200, Brendan Hide wrote:
On 2014/05/04 02:47 AM, Marc MERLIN wrote:
Is there any functional difference between
mount -o subvol=usr /dev/sda1 /usr
and
mount /dev/sda1 /mnt/btrfs_pool
mount -o bind /mnt/btrfs_pool
;Total" bytes used refers to the total actual data that is stored.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.ke
On 2014/05/04 09:28 AM, Marc MERLIN wrote:
On Sun, May 04, 2014 at 09:16:02AM +0200, Brendan Hide wrote:
Sending one-at-a-time, the shared-data relationship will be kept by
using the -p (parent) parameter. Send will only send the differences
and receive will create a new snapshot, adjusting for
On 2014/05/04 09:24 AM, Marc MERLIN wrote:
On Sun, May 04, 2014 at 08:57:19AM +0200, Brendan Hide wrote:
Hi, Marc
Raid0 is not redundant in any way. See inline below.
Thanks for clearing things up.
But now I have 2 questions
1) btrfs has two copies of all metadata on even a single drive
mentation to
include self-healing/scrubbing support - a critical issue before it can
be adopted further.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the
backup | btrfs receive $path/
$ btrfs send -p backup backup.sav1 | btrfs receive $path/
$ btrfs send -p backup.sav1 backup.sav2 | btrfs receive $path/
$ btrfs send -p backup.sav2 backup.sav3 | btrfs receive $path/
$ btrfs send -p backup.sav3 backup.sav4 | btrfs receive $path/
--
______
Br
recently-highlighted issue with old snapshots is the potential that old
vulnerable binaries within a snapshot are still accessible and/or
executable.
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscr
file is
only on a single disk, the allocation does mean that the majority of all
files smaller than a chunk will be stored on only one disk or the other
- not both.
Thanks,
Marc
I hope the above is helpful.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?
r with what Hugo and I last termed as "csp notation".
Changing the terminology is important - but it is particularly non-urgent.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
On 2014/04/16 05:22 PM, David Sterba wrote:
On Wed, Apr 16, 2014 at 04:59:09PM +0200, Brendan Hide wrote:
On 2014/04/16 03:40 PM, Chris Mason wrote:
So in my example with the automated tool, the tool really shouldn't be
deleting a snapshot where send is in progress. The tool should be
; for "parent", which you should
already be using for the backups in the first place:
From backup host:
$ btrfs send -p /backup/path/yesterday /backup/path/last_backup |
From restored host:
$ | btrfs receive /tmp/btrfs_root/
Then you make the non-read-only snapshot of the restored s
p for 3.16 and we can try it
out in -next.
-chris
So ... does this mean the plan is to a) have userland tool give an
error; or b) a deletion would be "scheduled" in the background for as
soon as the send has completed?
--
______
Brendan Hide
http://swiftspirit.co.za/
http:/
ffectively lost. btrfs
send optionally takes multiple clone sources, but I've never seen an
example of its usage.
If that's what "experimental" means, I'm willing to accept it. However,
I'd like to emphasize that there's still something missing. Of course,
m
have noticed this in your earlier mail. This
could be updated to specifically refer to the "bi"nary prefixes rather
than the old SI-conflicting names:
kibibyte, mebibyte, gibibyte, tebibyte, pebibyte, and exbibyte
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webaf
On 2014/03/27 04:51 AM, Gui Hecheng wrote:
[snip]
We add t/p/e support by replacing lib/cmdline.c:memparse
with btrfs_memparse. The btrfs_memparse copies memparse's code
and add unit t/p/e parsing.
Is there a conflict preventing adding this to memparse directly?
--
__
Brendan
I think) can be viewed here,
http://www.spinics.net/lists/linux-btrfs/msg23137.html where Hugo also
explains and lists the notation for the existing schemes.
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the li
as raid0) or to add a third disk.
In any raided configuration, the largest disk won't be fully utilised
unless the other disks add up to be equal to or more than that largest disk.
Play around with Hugo's disk usage calculator to get a better idea of
what the different configurations will d
On 2014/03/22 11:11 PM, Marc MERLIN wrote:
Please consider adding a blank line between quotes, it makes them just a bit
more readable :)
Np.
On Sat, Mar 22, 2014 at 11:02:24PM +0200, Brendan Hide wrote:
- it doesn't create writeable snapshots on the destination in case you want
to us
On 2014/03/22 10:00 PM, Marc MERLIN wrote:
On Sat, Mar 22, 2014 at 09:44:05PM +0200, Brendan Hide wrote:
Hi, Marc
Feel free to use ideas from my own script. Some aspects in my script are
more mature and others are frankly pathetic. ;)
There are also quite a lot of TODOs throughout my script
On 2014/03/22 09:44 PM, Brendan Hide wrote:
On 2014/03/21 07:29 PM, Marc MERLIN wrote:
Hi, Marc
Feel free to use ideas from my own script. Some aspects in my script
are more mature and others are frankly pathetic. ;)
There are also quite a lot of TODOs throughout my script that aren&#
t).
$ssh ls -rd $dest_pool/${vol}_ro* | tail -n +$(( $keep + 1 ))| while read snap
do
$ssh btrfs subvolume delete "$snap"
done
$ssh ls -rd $dest_pool/${vol}_rw* | tail -n +$(( $keep + 1 ))| while read snap
do
$ssh btrfs subvolume delete "$snap"
done
rm $lock
g that the other disk is part of the FS.
Notice that, though Disk C has the exact same files as it did before
step 1, the on-disk filesystem looks very different.
4. Follow steps 1, 2, and 3 above - but with different disks - similar
end-result.
--
__
Brendan Hide
http://swiftspirit.co.z
omated cleanup.
The only minor gripe I have with the temporary mount is that I feel it
should be possible to perform snapshots and use send|receive without the
requirement of having the subvolumes be "visible" in userspace.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://ww
rnel.org/index.php/Incremental_Backup for a
basic incremental methodology using btrfs send/receive
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a messa
opers to merge.
A list of the "main" repositories is maintained at
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories
I'd suggest David Sterba's branch as he maintains it for userspace-tools
integration.
--
__
Brendan Hide
http://swiftspirit.co.za/
h
ress could help.
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
uming sda and sdb:
btrfs balance start -dconvert=single -mconvert=dup /
btrfs device delete /dev/sdb /
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a m
-subvolume RAID profiles" you mentioned. It is difficult
to motivate including code (for which there's a known workaround) where
we know it will be obsoleted.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send th
,
the overall reliability of that array array plummets.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
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
s
bad enough that I simply bought my first SSD the same week.
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.or
actual size of my setup.
Could you send us the output of the following?:
btrfs fi df
(where is the path where the btrfs is mounted.)
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-
add it to the wiki:
https://btrfs.wiki.kernel.org/index.php/Project_ideas
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kerne
el.org/majordomo-info.html
This sounds to me like the problem is related to read performance
causing a bork. This would explain why bwlimit helps, as well as why cp
works the second time around (since it is cached).
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co
fs on top of an md-raid0?
cat /proc/mdstat
and
btrfs fi show
will answer those queries.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message
lly: every file passed an
md5sum check, in spite of tons of I/O errors in the process.
Is this all on a single disk? If so it must be seeking like mad! haha
--
______
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To unsubscribe from this list: send the line &qu
.
xC -> (x-1)C
xCmS -> (x/2)C(m*2)S
The complexity of the different types of conversions hasn't escaped me,
and I do see another downside as well. With the 3C->2C conversion there
is the inevitability of "macro" fragmentation. Again, there could be
long-
uot;mdraid stripe_cache_size".
To increase the read performance you can try optimising the md arrays'
readahead. As above, search online for "blockdev setra". This should
hopefully make a noticeable difference.
Good luck.
--
__
Brendan Hide
http://swiftspirit.co.
no point is failure of any of the /proc/swaps parsing fatal. It'd
carry on ignoring errors until it doesnt have work to do. It'd only
ever print the nice message when it finds a match.
--
__
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
--
To uns
journalctl -f
Alternatively, as another measure to troubleshoot, in
/etc/systemd/journald.conf, change the Storage= option either to "none"
(which disables logging completely) or to a path inside a tmpfs, thereby
eliminating btrfs' involvement.
--
__
Brendan Hide
1 - 100 of 108 matches
Mail list logo
