em here on this mailing
list, you'll get *most* of the experts looking at it, rather than just
the one, and you'll generally get a much better (and easier to use)
service.
Hugo.
--
Hugo Mills | The early bird gets the worm, but the second mouse
hugo@... carfax.org.u
;
> begin:vcard
> fn:Remi Gauvin
> n:Gauvin;Remi
> org:Georgian Infotech
> adr:;;3-51 Sykes St. N.;Meaford;ON;N4L 1X3;Canada
> email;internet:r...@georgianit.com
> tel;work:226-256-1545
> version:2.1
> end:vcard
>
--
Hugo Mills | Great oxymorons of the world, no. 8:
hugo@... carfax.org.uk | The Latest In Proven Technology
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
orted:
/srv/nfs/home -rw,async,fsid=0x1730,no_subtree_check,no_root_squash
It doesn't matter what value you use, as long as each one's
different.
Hugo.
--
Hugo Mills | Alert status mauve ocelot: Slight chance of
hugo@... carfax.org.uk | brimstone. Be prepared to make a nice cup of tea.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
node are passed to the kernel. The kernel holds a
lookup table of information for every device known of every
filesystem, and uses that table to work out which device nodes it
needs to use for any given FS.
Hugo.
--
Hugo Mills | Guards! Help! We're being rescued!
hugo@...
DEV && ret != BTRFS_ARG_REG) {
> > + if (ret < 0) {
> > + errno = -ret;
> > + error("invalid argument %s: %m",
> > argv[dev_optind]);
> > + } else {
> > +
s: No such file or directory
> ##
>
> I have a complete "dump tree" zip but its a couple of GB.
>
> Some sources on the net say to run "btrfs check --init-extent-tree" but I
> would like to reach out first.
Probably not wise. "Sources on the net&quo
pert
involved. (It's why there's no btrfs check fix for this situation --
you simply can't take the metadata broken in this way and make much
sense out of it).
Hugo.
> "usebackuproot,ro" did not succeed either.
>
> Much appreciate the input!
>
>
>
inode no. from
> > the tree dump that I have?
> >
> > "usebackuproot,ro" did not succeed either.
> >
> > Much appreciate the input!
> >
> > Sent with ProtonMail Secure Email.
> >
> > ‐‐‐ Original Message ‐‐‐
> > On Monday
kernel
what to do, rather than modifying the FS directly.
I'd say it's definitely worth fixing the issue upstream (which Qu
is doing), and then (if possible) backporting it to your maintained
packages after the Debian release.
[Other o
f8_general_ci,COERCIBLE) for operation '='
> (pdx-wl-lb-db.web.codeaurora.org)".
> =
>
> Any chance this can be conveyed to someone who can help please?
>
> Regards,
> William,
>
--
Hugo Mills | Would you like an ocelot with that non-sequ
ually exclusive with any option that might write to the FS, and if
it isn't any more, then it's been broken and needs fixing.
Hugo.
--
Hugo Mills | Great films about cricket: Interview with the Umpire
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
and it's
> ambiguous what the user wants (it's user error) and the command should
> fail with "conflicting options" error.
I already raised that question. :)
It was a typo in the email. --repair was what was intended.
Hugo.
--
Hugo Mills | G
an hand over the existing dataset if you want historical
continuity.
Hugo.
--
Hugo Mills | UDP jokes: It's OK if no-one gets them.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
o if you want me to run any experiments, including
> potentially destructive, including usage of custom patches to btrfs-progs to
> find out the reason of corruption, would be happy to help as much as I can.
>
> P.S. I'm riding latest stable and rc kernels all the time and during
9MiB
> Metadata, RAID1: total=757.00GiB, used=281.34GiB
> Metadata, DUP: total=22.50GiB, used=19.27GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
>
> sda and sdb are megaraid raid6 with BBU and both are optimal.
>
> Any tips? Thanks.
>
> sb
type, bad option, bad superblock on /dev/sdb4,
> missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog - try
> dmesg | tail or so.
> [root@localhost ghmitch]#
>
>
> I am attaching the output from journalctl
ring some ideas since the readmirror
> topic has come up a few times on the mailing list recently.
I did write up a slightly more concrete proposal on how to do this
algorithmically (plus quite a lot more) some years ago. I even started
implementing it, but I ran into problems of available time
y), so if anything's been removed, you'll be overestimating
the overall change in size.
> Any thoughts? I'm willing to implement such a feature in btrfs-progs if
> this sounds reasonable to you.
If you're looking for the incremental usage of the subvolume, why
not
the FS is at least
reasonably complete and undamaged. I don't think this will make a
difference. However, it's worth checking whether there are any
funnies about your encryption layer on ARM (I wouldn't expect any,
since it's recognising the decrypted device as btrfs, rather
s a detailed description of the issues of broken hardware on
the btrfs wiki, here:
https://btrfs.wiki.kernel.org/index.php/FAQ#What_does_.22parent_transid_verify_failed.22_mean.3F
Hugo.
--
Hugo Mills | Why play all the notes, when you need only play the
hugo@... carfax.org.uk | mos
updated the kernel, with no difference:
>
> $ uname -a
> Linux rescue 5.1.5-arch1-2-ARCH #1 SMP PREEMPT Mon May 27 03:37:39
> UTC 2019 x86_64 GNU/Linux
>
> Before making any recovery attempts, or even restoring from backup,
> I w
27;s
assume that they do for the purposes of this question).
Hugo.
--
Hugo Mills | The enemy have elected for Death by Powerpoint.
hugo@... carfax.org.uk | That's what they shall get.
http://carfax.org.uk/ |
PGP: E2AB1DE4 | gdb
signature.asc
Description: Digital signature
On Mon, Jun 10, 2019 at 04:02:36PM +0200, David Sterba wrote:
> On Mon, Jun 10, 2019 at 12:42:26PM +0000, Hugo Mills wrote:
> >Hi, David,
> >
> > On Mon, Jun 10, 2019 at 02:29:40PM +0200, David Sterba wrote:
> > > this patchset brings the RAID1 with 3 and 4 copi
t;, because you could do a load of
optimisation with reshaping the FS in userspace with that. But I
suspect it's a long way down the list of things to do.
> Or is there any obvious solution I'm completely missing?
I don't think so.
Hugo.
--
Hugo Mills | Great films about cricket: Umpire of the Rising Sun
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
On Tue, Jun 18, 2019 at 02:50:34PM -0400, Austin S. Hemmelgarn wrote:
> On 2019-06-18 14:45, Hugo Mills wrote:
> >On Tue, Jun 18, 2019 at 08:26:32PM +0200, Stéphane Lesimple wrote:
> >>I've been a btrfs user for quite a number of years now, but it seems
> >>I need
On Tue, Jun 18, 2019 at 07:14:26PM +, DO NOT USE wrote:
> June 18, 2019 8:45 PM, "Hugo Mills" wrote:
>
> > On Tue, Jun 18, 2019 at 08:26:32PM +0200, Stéphane Lesimple wrote:
> >> [...]
> >> I tried using the -ddevid option but it only instructs btrfs to
nhanced getopt to allow more loose order inside
> > subcomand while still can distinguish global option, will it be accepted
> > (if it's quality is acceptable) ?
>
> I think it's not worth updating the parser just to support an IMHO
> narrow usecase.
--
Hugo Mills
eb->start, found_start);
> >>ret = -EIO;
> >>goto err;
> >>}
> >> @@ -628,8 +628,8 @@ static int btree_readpage_end_io_hook(struct
> >> btrfs_io_bio *io_bio,
> >>}
> >>found_level =
ven
> media as well.
I started doing this a couple of years ago, but it turned out to be
impossible to keep even vaguely accurate or up to date, without going
round and bugging the developers individually on a per-release
basis. I don't think it's going to happen.
Hugo.
--
Hu
gt; --
>
> Here, your chunk logical bytenr is 13835461197824, and its physical
> bytenr is 13500327919616 and 13500361474048.
>
> My calculation is quite simple.
> Start1 = CR - CS + ST1
> Start2 = CR - CS + ST2
>
> Unless the superblock is incorrect, it is not p
rfs the devices have been resized?
> I did not find a rescan command. btrfs scan does not change anything.
> Do I really have to reboot?
btrfs fi resize :max /mountpoint
btrfs dev scan is just used to tell the kernel which devices
contain [parts of] which btrfs filesystems.
Hugo.
t; btrfs fi resize 1:max /srv/share/
> btrfs fi resize 2:max /srv/share/
>
> And now boths phydevices show the correct size.
>
> This sound really strange for me that I have to tell btrfs to resize
> just a single disk insteag of automatically resizing all disks...I bet
g this thing with fire and restoring from backup
(which will take a few weeks), does anyone else have any suggestions
for recovery?
Hugo.
--
Hugo Mills | "Can I offer you anything? Tea? Seedcake? Glass of
hugo@... carfax.org.uk | Amontillado?"
http://carfax.org.uk/ |
P
because
> to have any persistent paths, you need to remount using the new
> subvolume (generally means killing programs reading from it), or using
> paths that begin like /dir/b{1,2} and then renaming subvolumes, and then
> requesting that all reading programs reopen their files because the
nt to continue using btrfs send -p incremental backups after
the migration
- cry, because you can't
(*) For subvols S1, S2, S3, ...: btrfs send S1; btrfs send -c S1 S2;
btrfs send -c S1 -c S2 S3; btrfs send -c S1 -c S2 -c S3 S4; etc...
Hugo.
--
Hugo Mills |
gt; >of mismatched assumptions and layering inversions, using uninitialized
> >kernel data as mortar (though I suppose the "uninitialized" data symptom
> >might just have been an unprotected memory access).
> >
> >>Abuse of workquque to delay works and the full fs s
On Fri, Nov 18, 2016 at 04:06:22AM +0200, Marcus Sundman wrote:
> On 18.11.2016 02:52, Hugo Mills wrote:
> >On Fri, Nov 18, 2016 at 02:38:25AM +0200, Marcus Sundman wrote:
> >>The FAQ says that "the best solution for small devices (under about
> >>16 GB) is to
ots aren't going to need a system chunk much bigger than 1MB.
Again, the system chunk has *nothing* to do with snapshots.
Agreed with everything else, though.
Hugo.
--
Hugo Mills | I'm always right. But I might be wrong about that.
hugo@...
hunk tree. So you
definitely wouldn't want to use a 1 MiB chunk size for the system tree
in general. I don't see a problem with shrinking it for small
filesystems, though.
The only thing I can see might be an issue is where a small FS is
created with, say, a 128 KiB system chunk, and t
On Tue, Jan 10, 2017 at 11:05:17AM -0500, Austin S. Hemmelgarn wrote:
> On 2017-01-10 10:47, Hugo Mills wrote:
> >On Tue, Jan 10, 2017 at 10:42:51AM -0500, Austin S. Hemmelgarn wrote:
> >>Most of the issue in this case is with the size of the initial
> >>chunk. That
it to be updated? "Nope, still broken"?
Hugo.
- --
Hugo Mills | I went to a fight once, and an ice hockey match
hugo@... carfax.org.uk | broke out.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcB
ure requests, but it seems since this is something that was
> planned longer ago it's not documented. Can someone tell me where to
> find a list of feature priorities or when this might be done.
There isn't such a list (or at least, not a publicly acknowledged
one).
Hugo.
-
ose in most
cases.
Hugo.
> Cheers and thanks for any suggestions,
> Oliver
>
> PS: Please put my mail in CC, I'm not subscribed to the list. Thanks!
--
Hugo Mills | This: Rock. You throw rock.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Graeme Swann on fast bowlers
signature.asc
Description: Digital signature
On Thu, Jan 26, 2017 at 10:36:55AM +0100, Oliver Freyermuth wrote:
> Hi and thanks for the quick reply!
>
> Am 26.01.2017 um 10:25 schrieb Hugo Mills:
> >Can you post the output of "btrfs-debug-tree -b 35028992
> > /dev/sdb1", specifically the 5 or so entries a
needs to work, or,
> "doctor, if I push here it hurts; well, don't push there"...)
Definitely needs to work, but it's a rare use-case on most machines
(e.g. x86, arm, which covers the vast majority of machines out
there). sparc is the main one that I know of where a
the size of the
> > device is allocated for chunks.
> >
> > The value one line above is what is allocated inside the chunks.
> >
> > I.e. the line in "devid 1" is "total" of btrfs fi df summed up, and the
> > line
> > above is &
5.00GiB
>
> System,RAID1: Size:32.00MiB, Used:16.00KiB
>/dev/sda3 32.00MiB
>/dev/sdb3 32.00MiB
>
> Unallocated:
>/dev/sda3 1.00MiB
> /dev/sdb3 1.00MiB
>
>
> Version information:
>
> as
some upstream supplier, then they should
be giving you support and recommending what's usable in that kernel.
Hugo.
--
Hugo Mills | There are three mistaikes in this sentance.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
path /samba/home
> expire_proc: exp_proc = 1960834160 path /samba/home
> expire_cleanup: got thid 1960834160 path /samba/home stat 0
> expire_cleanup: sigchld: exp 1960834160 finished, switching from 2 to 1
> st_ready: st_ready(): state = 2 path /samba/home
> st_expire: state 1 path /-
> expire_proc: exp_proc = 1960834160 path /-
> expire_cleanup: got thid 1960834160 path /- stat 0
> expire_cleanup: sigchld: exp 1960834160 finished, switching from 2 to 1
> st_ready: st_ready(): state = 2 path /-
>
> Shadrock
>
>
--
Hugo Mills | My karma has run over my dogma.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
to balance the smaller (256 MiB nominal)
> metadata chunks first, hoping that frees the minimum 1 GiB space needed
> for a data chunk, or temporarily adding another device a few GiB in size
> to the filesystem, to give it somewhere to write the new chunk to so it
> can start off the rewrite and shrinking process.
>
--
Hugo Mills | Darkling's First Law of Filesystems:
hugo@... carfax.org.uk | The user hates their data
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
a bug report and a patch to keep it from using
> duplicate switches.
No, the duplicate -s is a valid part of the API.
One -s will replace the filenames with random data. A second one
will attempt to find a replacement name that matches the CRC32 hash of
the filename. That's why it
5.00GiB
>
> System,single: Size:32.00MiB, Used:16.00KiB
>/dev/sdb4 32.00MiB
>
> Unallocated:
>/dev/sdb4 28.91GiB
>
>
> ---
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüf
possible.
I hope that's of use to someone with more spare coding time than
me. And maybe we can finally have free space estimation that gets it
right...
Hugo.
--
Hugo Mills | A gentleman doesn't do damage unless he's paid for
hugo@.
On Fri, Mar 11, 2016 at 10:17:03PM +, Hugo Mills wrote:
>I know I promised this a while ago and didn't get round to it, but
> Henk's tinkering reminded me of it. I note specifically that the
> algorithm used to give the free space to plain old df gives incorrect
&g
marked as such in the FS (with the incompat flag "raid56"), and
attempting to mount that FS on a kernel that doesn't know about parity
RAID (earlier than 3.14, IIRC) will fail safely because the kernel
can't handle it.
Hugo.
--
Hugo Mills | Alert status upwards v
On Fri, Mar 18, 2016 at 05:31:51PM -0600, Chris Murphy wrote:
> On Fri, Mar 18, 2016 at 12:02 PM, Hugo Mills wrote:
> >The main thing you haven't tried here is mount -o degraded, which
> > is the thing to do if you have a missing device in your array.
> >
> >
RAID56 )
> csum_type 0
> csum_size 4
> cache_generation69462
> uuid_tree_generation69462
> dev_item.uuid 70f4650c-e01d-4613-bd7a-a6834c1c44bb
> dev_item.fsid 27ef2638-b50a-4243-80ed-40c3733ec11d [match]
On Fri, Mar 18, 2016 at 06:58:02PM +0100, David Sterba wrote:
> On Fri, Mar 11, 2016 at 10:17:03PM +0000, Hugo Mills wrote:
> >I know I promised this a while ago and didn't get round to it, but
> > Henk's tinkering reminded me of it. I note specifically that the
>
nstance of a btrfs
filesystem? "Filesystem" covers both cases.
Hugo, Ontologist(*).
(*) Yes, that's actually my job title these days.
--
Hugo Mills | Be pure.
hugo@... carfax.org.uk | Be vigilant.
http://carfax.org.uk/ | Behave.
PGP: E2AB1DE4 |
20:25:18 fan kernel: [ 20.981472] BTRFS error (device dm-16): could
> not find root 8
>
> which is not detected by btrfs check.
>
> What is going on here?
"Could not find root 8" is harmless (and will be going away as a
message soon). It just means that systemd is probing the FS for
quotas, and you don't have quotas enabled.
Hugo.
--
Hugo Mills | Hey, Virtual Memory! Now I can have a *really big*
hugo@... carfax.org.uk | ramdisk!
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
fs.wiki.kernel.org/index.php/Btrfs_design
[5] https://btrfs.wiki.kernel.org/index.php/Trees
--
Hugo Mills | "There's more than one way to do it" is not a
hugo@... carfax.org.uk | commandment. It is a dire warning.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
nce start /mnt/backup" but it takes hours and hours.
>
> I'm using linux 4.1.15
> btrfs-progs v4.1.2
Can you show us the output of both "sudo btrfs fi show" and "btrfs
fi df /mnt/backup", please?
Hugo.
--
Hugo Mills | The Creature from
urce
> snapshot that the script creates to backup from and then tell btrfs
> send that generation number + the destination snapshots.
> Well, or get larger SSDs or get rid of some data on them.
Those are the other options, of course.
Hugo.
--
Hugo Mills | The trouble w
ock on /dev/loop2,
>missing codepage or helper program, or other error
>In some cases useful info is found in syslog - try
>dmesg | tail or so
> $ echo $?
> 32
--
Hugo Mills | There's many a slip 'twixt wicket-keeper and gully.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
7;re going to do all the hard work of (2), then (3) is a
reasonable logical(?) extension.
On the other hand, what's wrong with simply using send/receive? It
gives you a data structure (a FAR-format send stream) which contains
everything you need to reconstruct a subvolume on a btrfs d
r one is not even aligned to 2.
> >
> >But you system still seems mountable as you succeeded in running
> >btrfs scrub.
> >
> >So I assume either the tree block is not a critical one or the
> >copy saved you.
> >
> >Thanks,
> >Qu
--
Hugo Mills
seems subvolumes doesn't work after raid1
> conversion
The balance should have made no difference.
How are you trying to mount the subvols? (What commands/fstab config?)
What errors do you get when trying to mount?
Hugo.
--
Hugo Mills | The Creature from the Bla
toms (mount doesn't report errors, but no mount
happens), I would guess that your problem is with systemd. It has a
bug where it sometimes unmounts things immediately after you've
mounted them.
Hugo.
--
Hugo Mills | "You know, the British have alway
the machine up
for a while. If the cache messages persist, clear it manually by
mounting once with -oclear_cache, then mount again once with
-ospace_cache, and again wait for it to rebuild.
Hugo.
> These messages appear on every boot.
> That they means? And how fix it?
>
> $ uname -r
affect your workload. There's
an Ubuntu kernel PPA you can use to get the new kernels without too
much pain.
Hugo.
--
Hugo Mills | I don't care about "it works on my machine". We are
hugo@... carfax.org.uk | not shipping your machine.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
14-05-04_Fixing-Btrfs-Filesystem-Full-Problems.html
>
> Unfortunately if it is a single device volume and metadata is
> 'dup' to remove the extra temporary device one has first to
> convert the metadata to 'single' and then back to 'dup' after
> removal.
s again?
Just as an aside -- it doesn't affect you here, but you might want
to be aware -- syslinux doesn't support multi-device btrfs. I've been
bitten by that before, and it's a consideration for you should you
wish to add another device to this FS. Also, I haven't tr
On Fri, Feb 10, 2017 at 06:05:57PM -0600, John Hendy wrote:
> On Fri, Feb 10, 2017 at 5:49 PM, Hugo Mills wrote:
> > On Fri, Feb 10, 2017 at 11:40:41AM -0600, John Hendy wrote:
> >> Greetings,
>
>
> >Just as an aside -- it doesn't affect you here,
0 01 00 00 31 c0 f6 83 78 0a 00
[ 578.715816] RIP []
qgroup_fix_relocated_data_extents+0x2b/0x2c0 [btrfs]
[ 578.715828] RSP
[ 578.715828] CR2: fe50
[ 578.715830] ---[ end trace 3153f530aca9e6aa ]---
--
Hugo Mills | Questions are a burden, and answers a prison for
hu
On Fri, Mar 10, 2017 at 12:23:37PM +, Hugo Mills wrote:
>Does anyone recall seeing this oops before? Is it something that
> can be fixed with a newer kernel? (I'm on a USB stick for this, so a
> new kernel is a major undertaking, and I'd like some reasonable
> expec
On Mon, Mar 13, 2017 at 10:22:04AM +0800, Qu Wenruo wrote:
>
>
> At 03/10/2017 08:23 PM, Hugo Mills wrote:
> > Does anyone recall seeing this oops before? Is it something that
> >can be fixed with a newer kernel? (I'm on a USB stick for this, so a
> >new kernel
tack to be fixed
so that it passes the EXDEV up to the mv command properly, and passes
the subsequent server-side copy (reflink) back down correctly.
Hugo.
--
Hugo Mills | I'm on a 30-day diet. So far I've lost 18 days.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
However, there are cases where some items of data can take *much*
longer to move. The biggest of these is when you have lots of
snapshots. When that happens, some (but not all) of the metadata can
take a very long time. In my case, with a couple of hundred snapshots,
some metadata chunks take 4+ ho
On Mon, Mar 27, 2017 at 03:20:37PM +0200, Christian Theune wrote:
> Hi,
>
> > On Mar 27, 2017, at 3:07 PM, Hugo Mills wrote:
> >
> > On my hardware (consumer HDDs and SATA, RAID-1 over 6 devices), it
> > takes about a minute to move 1 GiB of data. At that rate,
Schürz wrote:
> >Thanks for that explanation.
> >
> >I'm sure, i didn't understand the -c option... and my english is pretty
> >good enough for the most things I need to know in Linux-things... but
> >not for this. :-(
> >
> >
>
--
Hugo Mills
thing from it being a subvol, and you lose the ability
to move subvols/snapshots in and out of it cheaply with mv. Hence the
recommendation to use a directory.
Hugo.
--
Hugo Mills | O tempura! O moresushi!
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
on leading to a "broken" filesystem (say, an
undeletable directory), no.
> Also, if I understand correctly, checksum are not transferred
> through send/receive, therefor a corruption while transferring is
> possible (just like with rsync), right?
Correct.
Hugo.
--
Hu
e
> disks, and will be missing.
>
> In short, you can't remove more than one disk of a BTRFS RAID1 and still
> have all of your data.
Indeed.
Hugo.
--
Hugo Mills | Some days, it's just not worth gnawing through the
hugo@... carfax.org.uk | straps
h
Can I borrow your time machine? Would last Wednesday be OK?
Hugo.
--
Hugo Mills | We teach people management skills by examining
hugo@... carfax.org.uk | characters in Shakespeare. You could look at
http://carfax.org.uk/ | Claudius's crisis management techniques, for
PGP
x27;t
> running database software), they are essentially doing the same
> things at a low level.
I remember thinking, when I was learning about the internals of
btrfs, that it looked an awful lot like the high-level description of
the internals of Oracle which I'd just been learning
rs
>
> i could clear the disk and send it to anyone intrested in ;-)
Do you have anything likely to be writing with O_DIRECT during the
scrub? Specifically, databases and VMs. Possibly some kinds of
torrent/distributed downloads.
Hugo.
--
Hugo Mills | In event of Last Tr
ch works only at
> the subvolume level.
The solution to this problem is to use send -c repeatedly, sending
the subvolumes one at a time, with one -c option for every subvolume
that already exists on the receiving machine. So you'll do something
like this:
send snap1
send -c snap1 snap2
s
ify does the FS in question mount (read-write? read-only?)
> > and what are the kernel messages if it does not.
> >
--
Hugo Mills | Welcome to Hollywood, a land just off the coast of
hugo@... carfax.org.uk | Planet Earth
http://carfax.org.uk/ |
PGP: E2AB1DE4 |The Cat's Meow
signature.asc
Description: Digital signature
On Wed, May 10, 2017 at 10:40:31AM +0200, Stefan Priebe - Profihost AG wrote:
> Am 10.05.2017 um 09:40 schrieb Hugo Mills:
> > On Wed, May 10, 2017 at 09:36:30AM +0200, Stefan Priebe - Profihost AG
> > wrote:
> >> Hello Roman,
> >>
> >> the FS is mount
this. It's probably going to need something really long and/or
stressful to pick it up, though (one of the CPU stress tests, for
example, and also a good long run with a RAM tester -- 24 hours or
longer).
Hugo.
> Stefan
> Am 10.05.2017 um 11:08 schrieb Hugo Mills:
> > On We
nstruction of the trees, then restore. Too bad I already nuked
> mine, so can't experiment with that.
I suspect it's still only capturing metadata, rather than data.
Hugo.
--
Hugo Mills | Would you like an ocelot with that non-sequitur?
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
es.debian.org/sid/monitoring-plugins-btrfs
> >
> > And, of course the btrfs-heatmap program keeps being a fun tool to
> > create visual timelapses of your filesystem, so you can learn how your
> > usage pattern is resulting in allocation of space by btrfs, and so that
> &
On Sun, May 14, 2017 at 04:16:52PM -0700, Marc MERLIN wrote:
> On Sun, May 14, 2017 at 09:21:11PM +0000, Hugo Mills wrote:
> > > 2) balance -musage=0
> > > 3) balance -musage=20
> >
> >In most cases, this is going to make ENOSPC problems worse, not
> >
ing ones are probably
complicated to deal with in any way more elegant than just stopping.
I recall seeing someone's stats on BUG_ON locations a couple of
years ago, and btrfs had managed to get the number of locations down
below XFS (but no other FS). It's a kind of success, at least...
On Fri, May 19, 2017 at 05:47:48PM -0700, Marc MERLIN wrote:
> On Sat, May 20, 2017 at 12:37:47AM +0000, Hugo Mills wrote:
> > > Can I make another plea for just removing all those BUG/BUG_ON?
> > > They really have no place in production code, there is no excuse for a
>
On Fri, May 19, 2017 at 06:25:22PM -0700, Marc MERLIN wrote:
> On Sat, May 20, 2017 at 12:57:09AM +0000, Hugo Mills wrote:
> >I think from the POV of removing these BUG_ONs, it doesn't matter
> > which FS causes them. "All" you need to know is where the error
>
ce wiped that disk and done a fresh btrfs install on it, because I
> had to get some work done :)
>
> Marc
--
Hugo Mills | Essex: a branch of philothophy.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
but should be expanded to a
whole load of other data-leakage paths in generalised storage systems.
Overwriting file contents hasn't really been a reliable method of
erasing files for many years (if ever).
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk
> >>
> >> I just finished doing some testing to check: It will work, kinda sorta.
> >>
> >> You'll be forced to mount read-only, and any reads of file extents
> >> that existed on the missing disk will return an io error. As I
> >> unders
libblkid). You may also want to check out the
list of required build packages on the wiki at [1], just in case
you're missing any others.
Hugo.
[1]
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories#Dependencies
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net
201 - 300 of 1469 matches
Mail list logo
