ves any data in it to other chunks.
Once the chunk is empty, it's freed up. Now, when the data is moved,
it will typically go to any free allocated space first; only if there
isn't any free space allocated for data will more space be allocated.
So, the normal behaviour is that when you
gt; > may it disable checksumming only for newly written extents and keep for
> > reading existing ones?
>
> You can't apply chattr +C to any files of non-zero length, so by definition
> there won't be any pre-existing checksummed extents in that file.
>
> --
mo info at http://vger.kernel.org/majordomo-info.html
--
Hugo Mills | Comic Sans goes into a bar, and the barman says, "We
hugo@... carfax.org.uk | don't serve your type here."
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
s + new files) only 10GB a day it
> > will be enough to run this ever night.
> > The last option completly avoid the ENOSPC issue but produce aditional
> > workload for your harddrives.
> >
> > Note: you should avoid making snapshots during balance. Use a
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 message to majord...
iB, used=0.00B
>
>
> # df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda3 424G 137G 286G 33% /var/lib/lxd
>
>
>
> Tomasz Chmielewski
> https://lxadm.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
here back in the 2.x era (IIRC).
Hugo.
>
> Yeah I know, it's just much of this is non-obvious to users unfamiliar
> with this file system. And even I'm often throwing spaghetti on a
> wall.
>
>
> --
> Chris Murphy
> --
> To unsubscribe from this list
info->cleaner_kthread = kthread_run(cleaner_kthread, tree_root,
> "btrfs-cleaner");
> --
> 2.7.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to major
;s no distinction: Data and metadata both use
the same chunks. If those chunks are DUP, then both data and metadata
are duplicated, and you get half the space available.
Hugo.
--
Hugo Mills | Questions are a burden, and answers a prison for
hugo@.
ry valuable. I just said that I
> *prefer* to have that stuff on the BTRFS wiki and feel that is the
> right place for it.
> >
> >I bet Chris Mason and other BTRFS developers at Facebook have some idea on
> >what they use within Facebook as well. To what exte
o the new/empty drive, but
> during the delete `btrfs fi us` shows
> Unallocated:
> /dev/sdc1 16.00EiB
>
> so deleted partition is counted as maximum possible empty drive and
> blocks are relocated to it instead of new/empty drive? (kernel-4.7.2 &
> btrfs-progs-4.7.1
gen 708 top level 5 path cm13.0
> ID 259 gen 708 top level 5 path ccache
> ID 269 gen 708 top level 5 path omni
>
> I would like the ccache subvol to always be stored on the SSD, unless no
> disk space is available. Is that possible?
No, it isn't, sorry.
Hugo.
--
parameter to the block group, so that BGs know their own stripe
size. Then implement a balance filter so that you can read a BG (in
the old stripe size, which it knows about), and write a new BG with
the new stripe size and the old data (now restriped).
It was a long and somewhat struggling c
f the unallocated space on all the devices is similar, it
gets the answer nearly right. It seems to get worse as the imbalance
of unallocated space across the devices gets larger.
Hugo.
--
Hugo Mills | I know of three kinds: hot, cool, and
hugo@... carfax.org.uk | what-time-does
R x_n XOR p = 0
for corresponding bits in the n data volumes. With one data volume,
n=1, and hence p = x_1.
What's the problem? :)
Hugo.
> -Anand
>
>
> > Three disks in
> >RAID6 is similar, but has a slight advantage at the moment in BTRFS
> >because it&
ecessarily reflected in the real-life
usage of the devices. I think that if you're doing those calculations,
you really need to find out what the values quoted by the manufacturer
actually mean, first. (i.e. if you read all the data once a month with
a scrub, and allow the drive to identify
On Tue, Aug 09, 2016 at 07:41:42PM +, Hugo Mills wrote:
> On Tue, Aug 09, 2016 at 03:22:03PM -0400, Chris Mason wrote:
> >
> >
> > On 08/09/2016 03:11 PM, Hugo Mills wrote:
> > >On Tue, Aug 09, 2016 at 06:27:33PM +, Hugo Mills wrote:
> > >>On Tu
On Tue, Aug 09, 2016 at 03:22:03PM -0400, Chris Mason wrote:
>
>
> On 08/09/2016 03:11 PM, Hugo Mills wrote:
> >On Tue, Aug 09, 2016 at 06:27:33PM +0000, Hugo Mills wrote:
> >>On Tue, Aug 09, 2016 at 02:26:14PM -0400, Chris Mason wrote:
> >>>On 08/09/2016 02
On Tue, Aug 09, 2016 at 06:27:33PM +, Hugo Mills wrote:
> On Tue, Aug 09, 2016 at 02:26:14PM -0400, Chris Mason wrote:
> > On 08/09/2016 02:23 PM, Hugo Mills wrote:
> > > Hi, Chris,
> > >
> > >On Tue, Aug 09, 2016 at 02:02:20PM -0400, Chris Mason wrote
On Tue, Aug 09, 2016 at 02:26:14PM -0400, Chris Mason wrote:
> On 08/09/2016 02:23 PM, Hugo Mills wrote:
> > Hi, Chris,
> >
> >On Tue, Aug 09, 2016 at 02:02:20PM -0400, Chris Mason wrote:
> >>On 08/09/2016 01:27 PM, Hugo Mills wrote:
> >>> Over the we
Hi, Chris,
On Tue, Aug 09, 2016 at 02:02:20PM -0400, Chris Mason wrote:
> On 08/09/2016 01:27 PM, Hugo Mills wrote:
> > Over the weekend, I started doing some maintenance on my server: I
> >upgraded to 4.7.0, and I started deleting a device from my array,
> >prepar
el: [] ?
btree_invalidatepage+0x85/0x85
Aug 9 15:59:56 s_src@amelia kernel: [] ? kthread+0x95/0x9d
Aug 9 15:59:56 s_src@amelia kernel: [] ?
ret_from_fork+0x1f/0x40
Aug 9 15:59:56 s_src@amelia kernel: [] ?
init_completion+0x1d/0x1d
--
Hugo Mills | Great films about cricket: Monster's No-Ball
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
mantics after a power loss: all th
efiles that you'd written up to the point of the power loss actually
appear afterwards. (If this didn't happen, you could lose up to 30s of
writes from before the crash).
It's only very recently that there's been an option to prevent it,
whic
like look at the modification
time of a file, and then find the latest generation of any item
associated with that file, which would give you a time/inode pairing.
Do enough of those, and you'd have some kind of map that you could use
to approximate the time for a given genid.
Hugo.
--
Hugo Mil
of 'a',
> > even after having deleted 'b'. Is a way to look that up somehow?
>
> Actually it would also be interesting what happens with blocks in
> deleted b after the blocks in c are unshared? Are they garbage
> collected or do we have some orphan subv
at the ioctl(s) that would handle this?
>
>
> Thank you for your help!
>
>
--
Hugo Mills | Reintarnation: Coming back from the dead as a
hugo@... carfax.org.uk | hillbilly
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
On Wed, Jul 06, 2016 at 05:42:33PM +0200, Holger Hoffstätte wrote:
> On 07/06/16 17:20, Hugo Mills wrote:
> > On Thu, Jul 07, 2016 at 12:16:01AM +0900, Wang Shilong wrote:
> >> On Wed, Jul 6, 2016 at 10:35 PM, Holger Hoffstätte
> >> wrote:
> >>>
> > This is great, but can we please skip the "skipping .." messages?
> > Maybe it's just me but I really don't see the value of printing them
> > when they don't contribute to the result.
> > They also mess up the display. :)
>
> I don'
y did full volume rebalance, defrag, rebooted multiple times
> - still, "Error: out of disk space".
>
> To sum up:
> - my files sum to 1.6 TiB
> - disk usage is shown to be 1.71 TiB
> - volume size is 1.81 TiB
> - btrfs util shows I have ~98 GiB free space on the volume
e operation as soon as it finds a
> csum error ?
> And will I have the risk to "contaminate" the target BTRFS volume by
> using BTRFS send ?
A send stream is effectively just a sequence of filesystem commands
(mv, cp, cp --reflink, rm, dd). So any damage that it can do when
replaye
to create raid56 in mkfs.btrfs.
> Developers who want to test can just remove the ifdef and recompile
> the tools anyway.
> But if end-users have to recompile userspace, that really forces the
> point that "you
> really should not use this right now".
>
> 3, re
On Fri, Jun 24, 2016 at 10:52:53AM -0600, Chris Murphy wrote:
> On Fri, Jun 24, 2016 at 2:50 AM, Hugo Mills wrote:
>
> >Checksums are not parity, correct. However, every data block
> > (including, I think, the parity) is checksummed and put into the csum
> > tree.
>
On Fri, Jun 24, 2016 at 01:19:30PM +0300, Andrei Borzenkov wrote:
> On Fri, Jun 24, 2016 at 1:16 PM, Hugo Mills wrote:
> > On Fri, Jun 24, 2016 at 12:52:21PM +0300, Andrei Borzenkov wrote:
> >> On Fri, Jun 24, 2016 at 11:50 AM, Hugo Mills wrote:
> >> > On Fri, Ju
On Fri, Jun 24, 2016 at 12:52:21PM +0300, Andrei Borzenkov wrote:
> On Fri, Jun 24, 2016 at 11:50 AM, Hugo Mills wrote:
> > On Fri, Jun 24, 2016 at 07:02:34AM +0300, Andrei Borzenkov wrote:
> >> 24.06.2016 04:47, Zygo Blaxell пишет:
> >> > On Thu, Jun 23, 2016 at
raid56 code and
> > the number of distinct failure modes it seems to have.
> >
>
> Well, the problem is that parity block cannot be redirected on write as
> data blocks; which makes it impossible to version control it. The only
> solution I see is to always use full stri
stances (for example, you can't easily start a balance on a
> remote system via a ssh command, which is the specific use case I
> have).
There's quite a bit of infrastructure in the userspace tools to
deal with managing an asynchronous scrub. It would probably be worth
looking at that in the first instance to see if it can be reused for
balance.
Hugo.
--
Hugo Mills |
hugo@... carfax.org.uk | __(_'>
http://carfax.org.uk/ | Squeak!
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
ppears to be currently unused, so
> perhaps I will look at developing a group-aware allocator instead of
> just limiting the chunk width.
I made some design notes on a generalised approach for this a while
ago:
http://www.spinics.net/lists/linux-btrfs/msg33782.html
http://www.spinics.ne
given the way the
indexing works (concatenation of the key elements, resulting in
lexical ordering of keys), you'd still have to do exactly the same
work, only in the kernel instead. The only thing you really win is the
number of context switches.
It would really have to be a new ioctl, too. You can't change the
behaviour of the existing one.
Hugo.
> >
> > So, the important line here was: "...when the extent_item just
> > manages to squeeze in as last result into the current result buffer
> > from the ioctl..."
> >
>
>
--
Hugo Mills | "What are we going to do tonight?"
hugo@... carfax.org.uk | "The same thing we do every night, Pinky. Try to
http://carfax.org.uk/ | take over the world!"
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
er receiving an 'end cmd' marker in the stream.
>
> ie. all the context lines start with two spaces instead of one. I'll
> apply this patch manually but please have a look.
Looking at this, I suspect it's a consequence of sending it as
"Content-Type: format=flowe
ate
> the number that the split starts looping.
For reference for anyone replying, we've already had this
conversation as far as I could manage it on IRC a few days ago:
http://logs.tvrrug.org.uk/logs/%23btrfs/2016-05-29.html#2016-05-29T10:13:53
Hugo.
--
Hugo Mills | In o
configuration, applied
to the top of subvol 5. If the feature allows configuration on a
per-subvol or per-object basis, then there should also be a name for
the relevant xattr (also in the btrfs namespace) that can be created
on each object as required.
Hugo.
--
Hugo Mills | Kl
all CoW filesystems. There are
some mititgations that can be put in place (true CoW rather than
btrfs's redirect-on-write, like some databases do, where the original
data is copied elsewhere before overwriting; cache aggressively and
with knowledge of the CoW nature of the FS,
; >
>
> How balance decides where to put data from chunks it frees? I.e. let's
> say I have one free data chunk and 10 chunks filled to 10%. Will "btrfs
> ba start -dusage=10" pack data from all 10 chunks into single one, this
> freeing 10 chunks for fur
00B
> Device unallocated: 18.19TiB
> Device missing: 0.00B
> Used:0.00B
> Free (estimated):0.00B (min: 8.00EiB)
>
> btrfs --version ==> btrfs-progs v4.5.3-70-gc1c27b9
> kernel ==> 4.6.0
suspension, so it would be a really bad idea.
In general, this would be the use-case for LVM. However, that's a
dangerous operation with btrfs, because the snapshot ends up being
included in the original FS (because it has the same UUID), and thus
causes the kernel to get very confused, l
filesystem to another
> one, you can keep around the previous backup snapshot and do an
> incremental send against that, which will result in proper sharing
> of blocks. I used to use this before I decided that I wanted better
> space efficiency for backups than BTRFS can currently of
generation
> schemes, so we'll use a standard random number source or API.
>
> /dev/random gives about 1-2MB/s of random data on several machines I've
> tried.
Just use /dev/urandom?
See, e.g. http://www.2uo.de/myths-about-urandom/
Hugo.
--
Hugo Mills | Putting U back in Honor, Valor, and Trth.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
On Wed, May 25, 2016 at 04:00:00AM -0700, H. Peter Anvin wrote:
> On 05/25/16 02:29, Hugo Mills wrote:
> > On Wed, May 25, 2016 at 01:58:15AM -0700, H. Peter Anvin wrote:
> >> Hi,
> >>
> >> I'm looking at using a btrfs with snapshots to implement a ge
p), or, if you're writing your own, the safe
deduplication ioctl which underlies those tools.
Hugo.
--
Hugo Mills | Well, sir, the floor is yours. But remember, the
hugo@... carfax.org.uk | roof is ours!
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
. how can I have 244.8 GB unallocated when the
> table below clearly shows that there is as much as 1.29TiB
> unallocated does not appear to make sense to me at least...
This is exactly the issue. The Unallocated value(s) from btrfs fi
usage on at least RAID-10 are simply wrong, any
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
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
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
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
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
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
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
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
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
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
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 |
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
>
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 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.
> >
> >
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 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
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@.
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
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
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
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
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
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
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 &
an order other
than the (arbitrary) one it's sent in, you need to replay it on a
filesystem with receive.
Hugo.
--
Hugo Mills | You shouldn't anthropomorphise computers. They
hugo@... carfax.org.uk | really don't like that.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
have the advantage of redundancy of important files
> combined with the flexibility of the volume manager and shared disk space.
>
> Possible?
>
>
> GReetings
>
> Christian
>
--
Hugo Mills | "I don't like the look of it, I tell you.
On Tue, Feb 09, 2016 at 11:36:49PM -0800, Ian Kelling wrote:
> I searched the man pages, can't seem to find it.
> btrfs-balance can change profiles, but not show
> the current profile... seems odd.
btrfs fi df /mountpoint
Hugo.
--
Hugo Mills | Gentlemen! You ca
chunks are to be allocated, they devices are ordered by the
amount of free space on them. The chunks are allocated to devices in
that order.
So, if you have three equal devices, 1, 2, 3, RAID-1 chunks will be
allocated to them as: 1+2, 3+1, 2+3, repeat.
With one device larger than the others (say
ed of the tool, and it's hard to work out
which switches to use for any given desired output (if it supports
them at all). This _really_ needs fixing.
(I'm more than happy to do that hard thinking and write up a
detailed spec for it, BTW).
Hugo.
--
Hugo Mills
On Wed, Feb 03, 2016 at 02:17:06PM -0700, Chris Murphy wrote:
> On Tue, Feb 2, 2016 at 6:00 AM, Austin S. Hemmelgarn
> wrote:
> > On 2016-02-01 15:21, Hugo Mills wrote:
> >>
> >> On Mon, Feb 01, 2016 at 02:44:24PM -0500, Austin S. Hemmelgarn wrote:
> >>&g
tion to rebuild the initramfs -- I find I
don't have to on Debian, and Chris just gave the recipe for
distributions using dracut.
Hugo.
> Regards,
> Hendrik
>
> ---
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> https://www.avast.com/antivirus
prova0
> dr-xr-xr-x. 18 root root 4,0K 28 gen 15.30 ..
>
> I get:
>
> FilesystemSize Used Avail Use% Mounted on
> /dev/sdb 11T 11T256K 100% /data
>
> # btrfs fi df /data/
> Data, RAID1: total=10.90TiB, used=10.90TiB
> System, RAID1:
On Mon, Feb 01, 2016 at 11:02:42PM +, Duncan wrote:
> Hugo Mills posted on Mon, 01 Feb 2016 22:11:20 + as excerpted:
>
> > On Mon, Feb 01, 2016 at 10:31:47PM +0100, Hendrik Friedel wrote:
> >> Hello,
> >>
> >> I am running CentOS from a btrfs root
-f5f625480f394bdc90d6d3c06be7fb88
> root=UUID=f9de7c11-012e-4e5d-8b53-0e6d6c2916a3 ro
> rootflags=subvol=root crashkernel=auto rhgb quiet
> initrd16 /initramfs-0-rescue-f5f625480f394bdc90d6d3c06be7fb88.img
> }
>
> ### END /etc/grub.d/10_linux ###
>
> ### BEGIN /etc/grub.d/20_linux
On Mon, Feb 01, 2016 at 03:37:39PM -0500, Austin S. Hemmelgarn wrote:
> On 2016-02-01 15:21, Hugo Mills wrote:
> >On Mon, Feb 01, 2016 at 02:44:24PM -0500, Austin S. Hemmelgarn wrote:
> >>In the process of trying to debug issues I'm having on one of my
> >>syst
rnel 4.3.3 (at least, that's the version
> that
> works right now, I see the same errors on 4.4.1, but I have other issues
> there that are (hopefully) unrelated to BtRFS).
--
Hugo Mills | Charting the inexorable advance of Western
hugo@... carfax.org.uk | syphilisa
d
in the device tree. If one of those doesn't match up with a
currently-known device for that filesystem (as determined by btrfs dev
scan), then it's missing.
Hugo.
--
Hugo Mills | I gave up smoking, drinking and sex once. It was the
hugo@... carfax.org.uk | scariest 20 minutes of my life.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
s, the entire dmesg from device insertion,
> formatting, mounting, copying to then from, and device yanking is here
> (should be permanent):
> http://pastebin.com/raw/Wfe1pY4N
>
> And the copy did successfully complete anyway, and the resulting files
> have the same hashes as thei
s in the superblock to find the tree of tree
roots, and then follow that into the other trees (at which point, you
can start using the data structures page).
Hugo.
--
Hugo Mills | Comic Sans goes into a bar, and the barman says, "We
hugo@... carfax.org.uk | don't serve your t
I achieve that directly with BTRFS
> RAID10?
No, not at the moment.
Hugo.
--
Hugo Mills | Comic Sans goes into a bar, and the barman says, "We
hugo@... carfax.org.uk | don't serve your type here."
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
not. Familiar with leafs as a computing term, but don't even know
> what they are in the context of btrfs. If it's a single file, how do
> I use the corrupt leaf, bad key order block number to see what it
> corresponds to, like I did with btrfs inspect-internal with the
> inodes?
--
Hugo Mills | Talking about music is like dancing about
hugo@... carfax.org.uk | architecture
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Frank Zappa
signature.asc
Description: Digital signature
Isn't this an FAQ already? There is already a patch to rename the
RAID modes. It's been sitting in the progs patch queue for about 2
years, because none of the senior devs has acked it yet (since it's a
big user-visible change).
Hugo.
--
Hugo Mills | Talkin
Hugo.
> So whenever you do your recovery works, make sure that there's never a
> moment where more than one btrfs block device appears with the same
> UUID.
> Even when it's just for some seconds it may already cause corruption.
>
>
> Cheers,
> Chris.
--
> ID.
>
> This seem to confuse UDEV, because /dev/disk/by-uuid seem to show
> just one link, not two links to two disks.
>
> Is there a way to change the BTRFS ID (generate new one) that I can
> differentiate between the two disks on one host?
btrfstune, with -u or -U
H
ind root 8
> [ 25.855431] BTRFS: could not find root 8
> [ 25.856834] BTRFS: could not find root 8
> [ 25.860539] BTRFS: could not find root 8
> [ 25.862021] BTRFS: could not find root 8
> [ 29.778795] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
> …
On Mon, Dec 21, 2015 at 09:28:37AM +, Filipe Manana wrote:
> On Mon, Dec 21, 2015 at 8:14 AM, Hugo Mills wrote:
> > On Sun, Dec 20, 2015 at 07:26:07PM -0600, Donald Pearson wrote:
> >> I read an implication in a different thread that defrag and autodefrag
> >>
r each write, as well as just the piece
that's being written by userspace).
Hugo.
--
Hugo Mills | UNIX: Japanese brand of food containers
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
On Tue, Dec 15, 2015 at 09:27:12AM -0500, Austin S. Hemmelgarn wrote:
> On 2015-12-15 09:18, Hugo Mills wrote:
> >On Tue, Dec 15, 2015 at 08:54:01AM -0500, Austin S. Hemmelgarn wrote:
> >>On 2015-12-14 16:26, Chris Murphy wrote:
> >>>On Mon, Dec 14, 2015 at
s, including the copy. This doesn't say what
> >policy should happen next, just that at least it's known there's a
> >mismatch.
> >
> That gets tricky too, because for example you have stuff like flat
> files used as filesystem images.
>
> However,
f is actually quite frequently found in these tracebacks,
> because it's the method chosen to deliberately trigger them.
It's not just btrfs. Invalid opcode is the way that the kernel's
BUG and BUG_ON macro is implemented.
Hugo.
--
Hugo Mills | Great oxymorons of the world, no. 10:
hugo@... carfax.org.uk | Business Ethics
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
201 - 300 of 1469 matches
Mail list logo
