Duncan posted on Mon, 04 Apr 2016 04:45:16 + as excerpted:
> Kai Krakow posted on Mon, 04 Apr 2016 02:00:43 +0200 as excerpted:
>
>> Does this also implement "copy-back" - thus, it returns the hot-spare
>> device to global hot-spares when the failed device has
ently
available (no automated spare handling at all), and an implementation
must start somewhere, so as long as it's designed to be improved and
extended with the missing features over time, as has been indicated, it's
a reasonable first-implementation.
--
Duncan - List replies preferred. No H
only triggered on compressed content and was thus a specific
bug, and simply attributed it to btrfs not yet being fully stable and
believed that's what it always did with too many crc errors, even when
they should be recoverable from the good raid1 copy).
--
Duncan - List replies preferred
erent subdir or
using a different name for it matters at all. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line "unsub
Chris Murphy posted on Fri, 01 Apr 2016 23:43:46 -0600 as excerpted:
> On Fri, Apr 1, 2016 at 10:55 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>> Marc Haber posted on Fri, 01 Apr 2016 15:40:29 +0200 as excerpted:
>
>>> [4/502]mh@swivel:~$ sudo btrfs fi usage / O
nding on how deep into -musage= and -dusage= you have to go, and how
long it takes on your spinning rust, it may actually be faster to do the
mkfs and restore from backup in any case, but given what you posted so
far, it's not necessary yet, so your choice, based I guess on what you
think will b
ould be recommended on the LTS track,
or 4.4 or 4.5 on the current track.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send
If there's a V3 anyway, apparent typo:
s/Node code/No code/
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line "u
een incredibly stable, even on systems with hardware issues
that made most filesystems (including a then much less stable and mature
btrfs) unworkable.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master.&q
Jose Otero posted on Mon, 28 Mar 2016 22:30:56 +0200 as excerpted:
> Duncan, you are right. I have 8 GB of RAM, and the most memory intensive
> thing I'll be doing is a VM for Windows. Now I double boot, but rarely
> go into Win, only to play some game occasionally. So, I think I'll be
p? (i.e. this problem won't come back, will it?)
As should (now) be obvious from the above, yes, definitely. Most patches
to specific bugs also include fstests (originally xfstests, I don't
actually know if the name has actually changed or if the fstests
references I see are simply using an inform
nowden's of the world will be doing that sort of thing, among the
multitude of security options they must take.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To u
you've nailed it down so
nicely, a fix should be quickly forthcoming. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line "
ault is normally 60, IIRC.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body o
itr* before the image is reloaded, but at
least here, I prefer to avoid that sort of complexity as it increases
maintenance complexity as well, and as an admin I prefer a simpler system
that I understand well enough to troubleshoot and recover from disaster,
to a complex one that I don't really understand an
Martin Steigerwald posted on Sun, 27 Mar 2016 14:10:07 +0200 as excerpted:
> On Freitag, 4. März 2016 12:31:44 CEST Duncan wrote:
>> Dāvis Mosāns posted on Thu, 03 Mar 2016 17:39:12 +0200 as excerpted:
>> > 2016-03-03 6:57 GMT+02:00 Duncan <1i5t5.dun...@cox.net>:
>>
ber this as it's
a very clever and rather useful method-tool to have in the ol' admin
toolbox (aka brain). =:^)
I only wish I had thought of it, as it sure seems clear... now that
you described it!
Greatly appreciated, in any case! =:^)
--
Duncan - List replies preferred. No HTML msgs.
&qu
it's certainly a fix
worth having.
I'll simply refer you to previous discussion on the list for the patch,
as that's where I'd have to look for it if I needed it myself before it
gets mainlined.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a mast
fixes it, before possibly having you try various debugging patches to
hone in on the problem, if it doesn't, so he can hopefully duplicate the
problem himself, and ultimately come up with a fix.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a m
o be of more value than your data,
even if the data itself ends up being unrecoverable.
So either way you save what was of more value to you. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is you
--
I like the change, but typo in the commit comment... What filesystems
other than btrfs allow DUP? =:^) It's correct in the posting subject.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your
t created the existing filesystem, and (3) a clean start, blowing
away any chance of some bug lurking in the existing layout waiting to
come back and bite you after you've put all the work into those
rebalances, if you choose them over the clean start.
--
Duncan - List replies preferred. No H
ance problem, but I
want to cover it in a separate reply. Suffice it to say here that the
news isn't great, if this is your issue, as it's a known but somewhat
rare problem that has yet to be properly traced down and fixed.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program
cklist, because device paths are routinely symlinked.
I guess that's obvious from a kernel dev perspective, but perhaps not so
much from an admin-user perspective, where the device-path /is/ often
considered the device.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfre
he btrfs wiki could be quite
useful, to many.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line "unsubscribe linux-
ther, fixes to one might not carry over to the other,
etc.
Tho as you suggest, possibly with a transition period during which both
implementations are available, to work out any differences in results and/
or dramatically worse runtime cases.
Thanks. =:^)
--
Duncan - List replies preferred. No HTML
fs in the first place.
Which again is where that research I mentioned above comes in... if their
data is valuable enough to actually care enough to do it, of course...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the progra
fact, the usual
recommendation is at least two offsite backups, alternated such that if
tragedy strikes when you're updating the one, taking it out as well, you
still have the other one safe and sound, and will only lose the
difference since that alternating backup, even when both your workin
still have the problem. Alternatively, if you're
relying on your distro for support, rely on your distro, as we'll do what
we can to support older versions here, but when there's problems and
they're old as yours, the first recommendation is generally exactly as I
said, update and try again with
e (over five years) to actually be implemented.
So don't get your hopes up for anything too immediate, or even
intermediate term (2-5 years out), unless you get extremely lucky and the
devs see it as a way to implement something they already are working on
or that's already a high priority &quo
h the other devs in terms of timing,
etc. But that will definitely take significant time even if you do it,
and the alternating backup solution can be put to use as soon as you can
get another device plugged in and setup. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lo
mlinks before doing this check?
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the b
what
changed in each btrfs-progs release as well, and I could look it up there
if wanted to, but so can you, and I'm using the older raid1, not parity-
raid, so I don't have the direct personal interest in that info that you
might, so...)
--
Duncan - List replies preferred. No HTML msgs.
&
with news and
have a client to use on news.gmane.org, or simply have lynx around and
can follow the link above in it, you can find and grab the news article
for yourself.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the pro
for -s /does/ encourage people not to touch it at
all, separately, and there could be very good reasons to normally treat
system as metadata and process them as a combined unit, but even then, it
seems very odd to me to expose -s on its own, even if --force is
required, and not a parallel, say -M, for me
s is
precisely the information that btrfs send -p provides. If you can strip
the changes themselves out and what's left is either human readable or
can be processed to human readable, then it should be exactly what you're
after, the changed blocks, for data and metadata both.
--
Duncan - List
w free space, and am not sure
whether btrfs resize does it or not, so you might have to quickly create
a new partition and filesystem in the space again but leave the
filesystem empty, then fstrim it (or just make the filesystem btrfs,
since mkfs.btrfs automatically does a trim if it detects an s
Ole Langbehn posted on Fri, 18 Mar 2016 10:33:46 +0100 as excerpted:
> Duncan,
>
> thanks for your extensive answer.
>
> On 17.03.2016 11:51, Duncan wrote:
>> Ole Langbehn posted on Wed, 16 Mar 2016 10:45:28 +0100 as excerpted:
>>
>> Have you tried the autodef
But with no other attributes indicating issues, I remain clueless
as to what might have happened and why that 1-worst, particularly so
given the 0 threshold for that attribute and that it's an old-age
indicator rather than a fail indicator, but the device is neither that
old, nor as I said, in a
, in
ordered to narrow down the search a bit, so this was really helpful,
particularly the Crucial bit as I already know Intels aren't
realistically in my price range.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the pr
Pete posted on Fri, 18 Mar 2016 18:16:50 + as excerpted:
> On 03/18/2016 09:17 AM, Duncan wrote:
>> So btrfs raid1 has data integrity and repair features that aren't
>> available on normal raid1, and thus is highly recommended.
>>
>> But, raid1 /does/ m
tro for the
support it offers on btrfs on older code, if indeed it does offer that
support.
As I said, only extremely limited and general help, not specific to your
problem at all, but it's the best I can do, in the absence of replies
from others. Hope it's at least of some help.
--
Duncan - L
I have such a personal negative reaction to dedupe.
But precedent and current usage being what they are...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubsc
pete posted on Mon, 14 Mar 2016 23:03:52 + as excerpted:
> [Duncan wrote...]
>>pete posted on Sat, 12 Mar 2016 13:01:17 + as excerpted:
>>>
>>> Subvolumes are mounted with the following options:
>>> autodefrag,relatime,compress=lzo,subvol=>
&
ite what you actually intended, or if either you or
I misunderstood something somewhere along the line.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscrib
Marc Haber posted on Sun, 13 Mar 2016 22:05:37 +0100 as excerpted:
> On Sun, Mar 13, 2016 at 05:12:35PM +0000, Duncan wrote:
>> Marc Haber posted on Sun, 13 Mar 2016 12:58:10 +0100 as excerpted:
>> > I see the same metadata spread as with the old filesystem in btrfs fi
>&g
y case. If you know your ssd isn't one of the
deduping ones (as I do, here), you can of course overrule that by
specifying modes at mkfs.btrfs time.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is y
I recovered what I needed, even if
it did appear to work successfully.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line &
ready in use in kernel code, but if this /were/ the original
kernel code...
So I definitely understand your confusion, Qu, and have the same personal
preference even as a native English speaker. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a ma
io, btrfs check --repair
can't do more than inconvenience you a bit if it makes the problem worse
instead of fixing it, since you have current backups and will only need
to blow away the filesystem and recreate it fresh, in ordered to restore
them.
--
Duncan - List replies preferred. No
iscovered it, plug in phone autocorrect
on youtube some day when you have some time, and be prepared to spend a
few hours laughing your *** off!
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master.&qu
lly, I'd say
just require superuser privs (and/or appropriate filecaps and/or SEL
security labels) to create them as well, and avoid the whole problem.
Yes, it'll be limiting, but it's a limit that will avoid the entire
Pandora's box of permissions and security implications.
--
Duncan - List
ypto patches.
Call me a conspiracy nut, but don't be too surprised if someone's
introducing some product with btrfs and encrypted subvolumes a year or 18
months from now... I know I won't be! =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and
map, yes, but don't
expect to see anything in the near (-2-year) future, more like
intermediate (3-5) year future. In all honesty I don't seriously expect
it to be long-term future, beyond 5 years, but it's possible.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree
r someone's going to take advantage of it
in some way, perhaps, as with many DoS vulns, using it to deny critical
resources as a way to simplify some other more critical attack, and it'll
be in the headlines as an attack that worked and a zero-day that still
works.
--
Duncan - List replies prefe
ing.
Regardless, I believe we've definitely established that while it's in the
mainline kernel and is no longer experimental, there's still quite some
warning there, contrary to Mark Habor's claim otherwise. And indeed, if
following that warning literally, review and benchmarking is all he'd be
doing
to me, which makes it a new and interesting bug. But not being a dev,
that's about as far as I can take it. As CMurphy said, file a bug with
all the various information, and hope the devs can replicate and trace it
down.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonf
s due to a
device failure, that means a window during which additional device
failures isn't covered also 10 times longer than it should be. Not good
for the life of your data, for sure!
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if
ownership/perms/times, and symlinks, if you wish.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line "unsubscr
chance the filesystem in question was created by that bugged
mkfs.btrfs, don't even try to fix it, just get what you can off it and
recreate with a mkfs.btrfs without that bug, ASAP.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you u
suspect I'd have to play around with the ranges a bit to figure out what
numbers I should actually be supplying, as the filter descriptions in the
manpage are somewhat vague on this point.
(Anyone who knows where to actually find those numbers to plug in and/or
has useful examples, feel fre
times
makes sense. But the given reason, a bare wish to reduce writes to the
ssd, without support such as one of the above use-cases or something
similar, really doesn't make sense, at least on its face. I'll agree
with other posters on that.
--
Duncan - List replies preferred. No HTML msgs.
"
AIK it should be in 4.5, which is getting close to release, so if
you prefer to run 4.5-rcX to applying the patch yourself, that should
work as well.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he
Nicholas D Steeves posted on Thu, 03 Mar 2016 16:21:53 -0500 as excerpted:
> Hi Duncan,
>
>> Of course either way assumes you don't run into some bug that will
>> prevent removal of that chunk, perhaps exactly the same one that kept
>> it from being removed during the
Dāvis Mosāns posted on Thu, 03 Mar 2016 17:39:12 +0200 as excerpted:
> 2016-03-03 6:57 GMT+02:00 Duncan <1i5t5.dun...@cox.net>:
>>
>> You're issue isn't the same, because all your space was allocated,
>> leaving only 1 MiB unallocated, which isn't normally enough
priority so fast
they have little chance to be consolidated into whole 4K block writes.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this
eep up with the list discussion and current on your kernels,
and be aware there are still occasional corner-cases being worked out" as
a caveat, which it should be said, is only slightly stronger than the
general recommendation for btrfs itself.
--
Duncan - List replies preferred. No HTML msgs.
&
t here, as the level of support we can
provide on such old kernels, particularly when they're old enough that
btrfs was still experimental on them, really is quite limited, and the
chances that we won't be able to do much but tell you to try a (much)
newer kernel on any problems you have is very
he above balance commands should just remove it,
actually pretty fast, as there's only a bit of accounting to do to remove
it. And if they don't, then it /is/ a bug, but I'm guessing they will.
=:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a mas
errors even when there's tens or
hundreds of GiB of unallocated space, where you had only that 1 MiB.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe
ble quota stability?
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a me
Austin S. Hemmelgarn posted on Wed, 02 Mar 2016 08:43:17 -0500 as
excerpted:
> On 2016-03-01 16:44, Duncan wrote:
>> John Smith posted on Tue, 01 Mar 2016 15:24:04 +0100 as excerpted:
>>
>>> what is the status of btrfs raid5 in kernel 4.4? Thank you
>>
&
r of only trivial value regardless, you
don't have anything to lose, and even if raid56 mode /doesn't/ prove so
stable for you after all, you can still rest easy knowing you aren't
going to lose anything of value. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree
ade) and which I still use occasionally to look
up files I don't have installed, as here, says lxc-ls is part of the lxc
package, so that esearch candidate was correct. =:^)
So, umm... while I'm not a doctor, perhaps making or keeping that
appointment with your shrink might not be such a bad idea.
e max
snapshots per filesystem recommendations, or reconsider whether you need
quota functionality and turn it off, eliminating the existing quota data,
if you don't really need that functionality. =:^(
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a
Γιώργος Πάλλας posted on Sun, 28 Feb 2016 10:17:38 +0200
as excerpted:
> On 28/02/16 05:45, Duncan wrote:
>> Γιώργος Πάλλας posted on Sat, 27 Feb 2016 13:45:03 +0200
>> as excerpted:
>>
>>> Hi all.
>>>
>>> If I have a btrfs subvolume 'subv' and the
like it, it!" for you. =:^)
FWIW the fstab (5) manpage is the official documentation for it, but it
says effectively what I said above. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your maste
reserving
the -r option?), but it doesn't work yet.
However, it shouldn't be horribly difficult to hack up scripts that
automate the otherwise manual recursive-send/receive for you, as I'd very
likely do myself if I needed that functionality. =:^)
--
Duncan - List replies preferred. No H
least here on-list, if you're not planning to keep
to the recommended last two kernel release series of either current or
LTS.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Sta
urprising. No explanation, there, tho I don't know enough
about such errors to know if they /always/ tend to show up in the logs,
or not, only that mine generally have.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the progr
Duncan posted on Tue, 23 Feb 2016 23:17:06 + as excerpted:
> Marc MERLIN posted on Tue, 23 Feb 2016 13:59:11 -0800 as excerpted:
>
>> I have a freshly created md5 array, with drives that I specifically
>> scanned one by one block by block, and for good measure, I also sca
ge
in that area, including what to do to try to fix it, than I have, and the
various options to fix it have been posted multiple times by now, and
likely will be posted here again.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if y
(Click the topic link on the left to see the
individual patches, which here don't include individual changelogs as
they're in the 00/19 post.)
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/53306
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord,
er or similar storage, an intermediate encryption step could be
added, with encryption to whatever strength deemed appropriate, if
considered necessary to thwart the NSA and similar nation-level advanced-
persistent-threats on cloud-hosted storage.
--
Duncan - List replies preferred. No HTML msgs.
&qu
meone who appreciates
the usefulness of btrfs restore, I definitely like the idea! =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send th
tweak, even if it's
not exactly the code a real C coder would choose to use, which is exactly
what I've done here. So now, unless some other atime option is
specified, my filesystems are all mounted noatime. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program
rleaved in context under each point you're replying to, further
replies and their context would have been far clearer for others reading
and replying.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is you
de. Or just do what I
did and browse around a bit until you figure out which of the listed repos
you're actually after. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
-
ply hasn't made it into a
stable release yet, that's understandable, tho having it specifically
stated, thus making waiting for it to hit stable an option, would be
nice. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you
ing that's not yet
full width, thereby evening out your usage.
A full balance /should/ do it as well, I believe, but with raid56 support
still not yet at the maturity level of btrfs in general, it's likely your
version is old and buggy in that regard.
--
Duncan - List replies preferred. N
n if they aren't current, unless one of the devs takes an
interest and you can build and run various debugging patches to trace
down the problem further and hopefully eventually get a btrfs check patch
that will fix it.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree progr
y and not
reliable anyway. So the recommendation is to leave quotas off on btrfs,
and use some other more mature filesystem where they're known to work
reliably if you really need them.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
an
h closer than I am (my
use-case doesn't involve snapshotting or subvolumes) will be along
shortly with further details and likely a link to the patch, but
meanwhile, yes, I think that's the bug that has already been tracked and
patched, and it only remains to get that patch out on what people are
rfs send -c. You're
still sending a subvolume, but the -c says to consider the supplied clone-
src parameter for just that, cloned, aka shared, sources, and unlike
-p parent, multiple such -c cloned-src options are allowed, so...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonf
Stefan Priebe posted on Sat, 13 Feb 2016 07:51:03 +0100 as excerpted:
> while running 4.4 i got the following enospc error today:
I don't see the usual btrfs fi sh and btrfs fi df
output included, that would show exactly what btrfs thought the
free-space situation was.
--
Duncan - L
s of any significant size, where the proportional space wastage of
sub-block tails will be far smaller.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe
copies can't be on the same device, which means that odd device can't be
used for that allocation round, tho it will be for the next, and a
different device left out instead.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the prog
Of course these days I use multi-device btrfs directly, no mdraid, and a
multi-device btrfs root unfortunately does seem to require an initr*, but
its other advantages outweigh the additional complexity of having to use
an initr*, so...
--
Duncan - List replies preferred. No HTML msgs.
"
, I think it doesn´t need to recreate
> the filesystem.
>
> I wonder what happened to the VFS hot data tracking stuff patchset
> floating around here quite some time ago.
AFAIK it's still around, and very possibly in-use by some major user. I
believe it's still on the btrfs roadmap and
r adding new devices so existing
stripes are rewritten broader, over the new devices as well (and
similarly, btrfs device remove will trigger a reshape-rebalance to narrow
the stripes and put the data that was on that removed device elsewhere)
but as mentioned above, at least right now, some peo
501 - 600 of 1780 matches
Mail list logo
