: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
lesystems, btrfs, or instance 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
> > a
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]
> dev_item.type 0
> dev_
On Fri, Mar 18, 2016 at 05:31:51PM -0600, Chris Murphy wrote:
> On Fri, Mar 18, 2016 at 12:02 PM, Hugo Mills <h...@carfax.org.uk> 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 a
(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 vermilion: High probability of
hugo@... c
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
> results
omeone 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@... carfax.org.uk | it.
http://carfax.org.uk/ |
PGP: E2
0GiB
>
> 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üft.
> ht
rogress.
>
> Could be worth 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
ks 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
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
mending 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
e:32.00MiB, Used:16.00KiB
>/dev/sda3 32.00MiB
>/dev/sdb3 32.00MiB
>
> Unallocated:
>/dev/sda3 1.00MiB
>/dev/sdb3 1.00MiB
>
>
> Version information:
>
> async@riff:~$ uname -a
> Linux riff 4.2.0-30-
t; > 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 "used" in b
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."
hug
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 can't f
y 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, device 3), it'll start
as: 3+1,
d 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 | How do you become King? You st
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
> <ahferro...@gmail.com> wrote:
> > On 2016-02-01 15:21, Hugo Mills wrote:
> >>
> >> On Mon, Feb 01, 2016 at 02:44:24PM -0500, Austin S. Hemmelga
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
>
--
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: total=8.00MiB, used=1.50MiB
> Metadata, R
he 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 | syphilisation.
http://carfax.org.uk/ |
PGP:
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
> >>systems w
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 ro
hkernel=auto rhgb quiet
> initrd16 /initramfs-0-rescue-f5f625480f394bdc90d6d3c06be7fb88.img
> }
>
> ### END /etc/grub.d/10_linux ###
>
> ### BEGIN /etc/grub.d/20_linux_xen ###
>
> ### END /etc/grub.d/20_linux_xen ###
>
> ### BEGIN /etc/grub.d/20_ppc_terminfo ###
> #
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
erblock 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 type here."
http
uestion is: can 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
e 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 their originals. So, yay, despite
e the same
> 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
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 | Talking about music i
> 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.
--
Hugo Mills |
, 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
oot 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 <h...@carfax.org.uk> wrote:
> > On Sun, Dec 20, 2015 at 07:26:07PM -0600, Donald Pearson wrote:
> >> I read an implication in a different thread that defrag an
te, 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
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, if we then use some separate UUID (possibly hashed off of
> the file location) in place of the device serial/WWN, th
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
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
t anywhere near as simple as copying it with dd. The UUID
> gets used internally somehow, and changing it would require rewriting
> _all_ the metadata blocks.
Indeed, but there is now a tool to do that. :) (btrfstune -u or -U)
Hugo.
--
Hugo Mills | Go not to the elves for counsel, for they will say
hugo@... carfax.org.uk | both no and yes.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
fs scrub start /t4
> ERROR: scrub is already running.
> To cancel use 'btrfs scrub cancel /t4'.
> To see the status use 'btrfs scrub status [-d] /t4'.
>
>
--
Hugo Mills | Go not to the elves for counsel, for they will say
hugo@... carfax.org.uk | both no and yes.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
On Sat, Dec 05, 2015 at 04:28:24AM +0100, Christoph Anton Mitterer wrote:
> On Fri, 2015-12-04 at 13:07 +0000, Hugo Mills wrote:
> > I don't think it'll cause problems.
> Is there any guaranteed behaviour when btrfs encounters two filesystems
> (i.e. not talking about
d function correctly
when received. (I can give you chapter and verse on how they're used
if you like, but that's a bit excessive just for answering your
question here).
Hugo.
> Thank you
>
> PS: Apologies for sending a second mail, somehow my first try didn't contain
> any
or ext4 support removing the
> norecovery option from the mount flags through mount -o remount?
> Even if they don't, that might be a nice feature to have in BTRFS if
> we can safely support it.
One minor awkwardness with "norecovery", I've just realised: we
already h
to implement it first for non-remountable case as a try.
> And for the option name, I prefer something like "notreereplay", but
> I don't consider it the best one yet
Thinking out loud...
no-log-replay, no-log, hard-ro, ro-log,
really-read-only-i-mean-it-this-time-honest-guvnor
Delete hyphens at your pleasure.
Hugo.
--
Hugo Mills | ORLY? IÄ! R'LYH!
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
On Mon, Nov 30, 2015 at 11:48:01AM -0500, Chris Mason wrote:
> On Sat, Nov 28, 2015 at 01:46:34PM +0000, Hugo Mills wrote:
> >We've just had someone on IRC with a problem mounting their FS. The
> > main problem is that they've got a corrupt log tree. That isn't the
> >
On Mon, Nov 30, 2015 at 09:59:40AM -0500, Austin S Hemmelgarn wrote:
> On 2015-11-28 08:46, Hugo Mills wrote:
> >We've just had someone on IRC with a problem mounting their FS. The
> >main problem is that they've got a corrupt log tree. That isn't the
> >subject
btrfs --convert=single --force balance, btfs
> device remove, btr balance start -mconvert=dup --force and finally
> balance start again.
>
> Is there any solution to solve this more elegantly?
Recreate the FS with --mixed, and that should deal with it.
Hugo.
--
Hugo Mills | There isn't a noun that can't be verbed.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
We've just had someone on IRC with a problem mounting their FS. The
main problem is that they've got a corrupt log tree. That isn't the
subject of this email, though.
The issue I'd like to raise is that even with -oro as a point
option, the FS is trying to replay the log tree. The dmesg
That's the quota tree. I don't know exactly what's happening, but
possibly systemd is now enabling qgroups for its own purposes, and
what you're seeing is simply the qgroups being enabled for the first
time?
Hugo.
--
Hugo Mills | Great oxymorons of the world, no. 8:
hugo@... carfa
expect
> it (e.g. the defrag or the balance+compression case?)... btrfs seem to
> require much more in-depth knowledge and especially care (that even
> depends on the type of data) on the end-user/admin side than the
> traditional filesystems.
> Are there for example any gene
s.
Hugo.
> Thank you!
> Mario
>
> [1]
> http://git.kernel.org/cgit/linux/kernel/git/mkp/linux.git/commit/?h=bugzilla-93581=7c4fbd50bfece00abf529bc96ac989dd2bb83ca4
> [2] https://bugzilla.kernel.org/show_bug.cgi?id=93581
--
Hugo Mills | I was cursed with poetry very youn
fy the disk
data after an unclean shitdown, in order to be useful (because the FS
isn't consistent without the journal replay).
Hugo.
--
Hugo Mills | I'll take your bet, but make it ten thousand francs.
hugo@... carfax.org.uk | I'm only a _poor_ corrupt offici
On Wed, Nov 25, 2015 at 12:20:09AM +0100, Christoph Anton Mitterer wrote:
> On Tue, 2015-11-24 at 21:55 +0000, Hugo Mills wrote:
> > In practice, new content is checked by a number of people when
> > it's
> > put in, so the case of someone putting random poorly-thought-out
On Wed, Nov 25, 2015 at 12:01:49AM +0100, Christoph Anton Mitterer wrote:
> On Tue, 2015-11-24 at 22:33 +0000, Hugo Mills wrote:
> > whereas a read-only mount of a journalling FS _must_ modify the disk
> > data after an unclean shitdown, in order to be useful (because the FS
>
parent IDs accordingly...
Pretty much, yes.
Note that the "parent" of send -p and of snapshots is not the same
relationship as the "parent" (containing subvol) of the tree
structure. This is an awkward nomenclature problem, and I'm not sure
how to fix it.
The first m
(writable)
snapshot of the reference subvol, and modifies it according to the
stream data. -c makes a new empty subvol, and populates it from
scratch, using the reflink ioctl to use data which is known to exist
in the reference subvols.
Hugo.
--
Hugo Mills | Anyone who claims
; >total extent tree bytes: 3075457024
> >btree space waste bytes: 2880474254
> The only other thing I know that's worth mentioning is that if the
> numbers on these next two lines don't match, you may be missing some
> writes from right before the crash.
> >file data blocks al
On Tue, Nov 24, 2015 at 10:36:26PM +0100, Christoph Anton Mitterer wrote:
> On Tue, 2015-11-24 at 21:27 +0000, Hugo Mills wrote:
> > -p only sends the file metadata for the changes from the reference
> > snapshot to the sent snapshot. -c sends all the file metadata, but
&g
s that by
> >> default. Never heard of snapper before.
> >>
> >> Don't see how open files could be a problem, since the computer has
> >> been rebooted several times.
> >>
> >> I wonder... could the distribution upgrade have moved all the old
> &g
> >>would lose the fact that global reserve is actually in use, that the
> >>broken out global reserve line exposes.
> >>
> >>I'd actually argue in favor of the latter, directly folding global
> >>reserve allocation into metadata used, sinc
er. This is typically too much data
allocation, and metadata has run out (so -d is more often used than
-m).
For the "usual" case of running out of metadata allocation, you
don't actually need much space to reclaim, so -dlimit=X for small X is
an easier approach to
> ZFS since the very first day. With snapshots & all the fancy stuff like
> ZRAID-1, lz4, ... My number of Issues there: 0
>
--
Hugo Mills | Close enough for government work.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
l
> and restarting services, and old job don't die because they stuck in
> uninterruptable wait... etc.
>
> Tried with nodatacow, but it seems only affect new file. It is not an
> subvolume option either...
>
>
> Regards,
> Daniel
>
>
> [1] https://btrfs.wiki.kernel.
On Fri, Nov 13, 2015 at 02:40:44PM -0500, Austin S Hemmelgarn wrote:
> On 2015-11-13 13:42, Hugo Mills wrote:
> >On Fri, Nov 13, 2015 at 01:10:12PM -0500, Austin S Hemmelgarn wrote:
> >>On 2015-11-13 12:30, Vedran Vucic wrote:
> >>>Hello,
> >>>
> >
I have done
> >>>btrfs balance / -dusage=0 -musage=0
> >>>increasing value up to 4o I did not have issues.
> >>>But on value 4- for-dusage= and -musage=
> >>>I got message that there is no space left on disk.
> >>>Do you hav
:
>
> mount |grep sda
> /dev/sda6 on / type btrfs
> (rw,relatime,compress=lzo,space_cache,subvolid=257,subvol=/@)
> /dev/sda5 on /boot type ext4 (rw,relatime,data=ordered)
> /dev/sda7 on /home type btrfs
> (rw,relatime,compress=lzo,space_cache,subvolid=257,subvol=/@home)
>
On Fri, Nov 13, 2015 at 09:11:46PM +, Duncan wrote:
> Hugo Mills posted on Fri, 13 Nov 2015 19:55:20 + as excerpted:
>
> > receive is implemented almost exclusively in userspace, with only a
> > couple of ioctls for mucking around with the UUIDs at the end.
&
UID=""
> >>> NAME="sdi1" MODEL="" SERIAL="" SIZE="500M" TRAN="" VENDOR="" HCTL=""
> >>> TYPE="part" FSTYPE="ext4" LABEL=""
> >>> UUID="53aabf2f-5e28-4a18-922f-b0767a77a8ec"
> >>> NAME="sdi2" MODEL="" SERIAL="" SIZE="7.3G" TRAN="" VENDOR="" HCTL=""
> >>> TYPE="part" FSTYPE="swap" LABEL=""
> >>> UUID="bf9e72c7-7d72-4a33-a5eb-0a0013033234"
> >>> NAME="sdi3" MODEL="" SERIAL="" SIZE="66.8G" TRAN="" VENDOR="" HCTL=""
> >>> TYPE="part" FSTYPE="btrfs" LABEL="rockstor_rockstor"
> >>> UUID="3533171e-d95b-4491-aa4c-cc956536a1c3"
> >>> [root@rockstor ~]#
> >>>
> >>>
> >>>
> >>>
> >>> [root@rockstor ~]# btrfs fi show
> >>> Label: 'rockstor_rockstor' uuid: 3533171e-d95b-4491-aa4c-cc956536a1c3
> >>> Total devices 1 FS bytes used 2.17GiB
> >>> devid1 size 66.79GiB used 7.02GiB path /dev/sdi3
> >>>
> >>> Label: 'seagate3x2tb' uuid: 6ef19043-2d83-4ff1-b959-b9f3c425cc69
> >>> Total devices 3 FS bytes used 1.13TiB
> >>> devid1 size 1.82TiB used 595.03GiB path /dev/sdh
> >>> devid2 size 1.82TiB used 595.01GiB path /dev/sdf
> >>> devid3 size 1.82TiB used 595.01GiB path /dev/sdg
> >>>
> >>> Label: 'mainNAS' uuid: e8c92d93-fac3-4f83-b3aa-31cb92caafd9
> >>> Total devices 5 FS bytes used 5.43TiB
> >>> devid1 size 2.73TiB used 1.36TiB path /dev/sdd
> >>> devid2 size 2.73TiB used 1.36TiB path /dev/sdc
> >>> devid3 size 2.73TiB used 1.36TiB path /dev/sda
> >>> devid4 size 2.73TiB used 1.36TiB path /dev/sde
> >>> devid5 size 2.73TiB used 1.36TiB path /dev/sdb
> >>>
> >>>
> >>> btrfs-progs v4.2.1
> >>>
> >>> I'm unable to mount any of the drives that are in the mainNAS array, this
> >>> is the error when I try to mount all of the drives degraded.
> >>>
> >>> [root@rockstor ~]# mount -v -o degraded /dev/sdd /mnt2/mainNAS
> >>> mount: wrong fs type, bad option, bad superblock on /dev/sdd,
> >>>missing codepage or helper program, or other error
> >>>In some cases useful info is found in syslog - try
> >>>dmesg | tail or so.
> >>> [root@rockstor ~]#
> >>>
> >>> I haven't given up hope yet as the "btrfs fi show" gives me all the
> >>> correct data and I ran chunk-recover and superblocks all report back as
> >>> good.
> >>>
> >>>
> >>> Thanks for your help, let me know if you need any further information.
> >>>
> >>> Thanks,
> >>>
> >>> Scotty Edmonds
> >>> sco...@scottyedmonds.com
--
Hugo Mills | "How deep will this sub go?"
hugo@... carfax.org.uk | "Oh, she'll go all the way to the bottom if we don't
http://carfax.org.uk/ | stop her."
PGP: E2AB1DE4 | U571
signature.asc
Description: Digital signature
ly, but only when David's in
a position to deal with the issues of changing the send stream.
Hugo.
--
Hugo Mills | "No! My collection of rare, incurable diseases!
hugo@... carfax.org.uk | Violated!"
http://carfax.org.uk/ |
PGP: E2AB1DE4 |Stimpson J. Cat, The Ren & Stimpy Show
signature.asc
Description: Digital signature
RFS info (device sdc3): disk space caching is enabled
> [ 3403.721098] BTRFS: has skinny extents
> [ 3413.964033] BTRFS info (device sdb3): disk space caching is enabled
> [ 3413.964042] BTRFS: has skinny extents
> [ 3522.902309] BTRFS info (device sdb3): disk space caching is enab
FS.
Hugo.
--
Hugo Mills | Nostalgia isn't what it used to be.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
dev_item.sector_size 4096
> dev_item.devid1
> dev_item.dev_group0
> dev_item.seek_speed 0
> dev_item.bandwidth0
> dev_item.generation 0
>
> =
>
> dmesg contains a lot of information which is superfluous to btrfs and
> personal, I can filter on a regex and report if necessary.
>
--
Hugo Mills | There are three things you should never see being
hugo@... carfax.org.uk | made: laws, standards, and sausages.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
[66031.291635] [] ret_from_fork+0x3f/0x70
> [66031.291637] [] ? kthread_worker_fn+0x170/0x170
> [66031.291638] ---[ end trace c69e578c3752000c ]---
> [66031.291640] BTRFS: error (device sdb) in cleanup_transaction:1710:
> errno=-5 IO failure
> [66031.291642] BTRFS info (device sdb
On Sat, Oct 31, 2015 at 06:31:45PM +0100, Simon King wrote:
> Hi Hugo,
>
> Am 31.10.2015 um 17:41 schrieb Hugo Mills:
> >> linux-va3e:~ # uname -a
> >> Linux linux-va3e.site 3.16.7-29-desktop #1 SMP PREEMPT Fri Oct 23
> >> 00:46:04 UTC 2015 (6be6a97) x86_64 x8
On Sat, Oct 31, 2015 at 04:26:11PM +0100, Simon King wrote:
> Hi!
>
> From the messages I see in this forum, I got the impression that it is a
> developer forum and not a help forum. I seek help. So, please point me
> to the right place if I shouldn't ask my questions here.
No, you're good
balancing, the numbers can be much different and then balance might be
> usefull.
If you're hitting ENOSPC with unallocated space, then that's a
bug. In fact, it's a known bug that hasn't been fixed yet.
Hugo.
--
Hugo Mills | That's not rain, that's a lake with slots in it.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
s this sort of thinning
> strategy will as well allow you to copy and dedup only key snapshots, say
> weekly plus daily for the last week, doing the backup thing manually, as
> well, modifying the thinning strategy accordingly if necessary to get it
> to fit. Tho using the copy and d
tem freezes totally. I recognized, it always
> >> happens during btrfs-balance.
> >>
> >> So i deleted some of the old snapshots and tried another balance-run.
> >> Nothing happened... No system-freeze.
> >>
> >> System-freeze means: No Keyboa
sts, because randomization, by definition
> does /not/ lend itself to duplication.
For what it's worth, David tried implementing round-robin (IIRC)
some time ago, and found that it performed *worse* than the pid-based
system. (It may have been random, but memory says it was round-robin).
Hugo.
--
Hugo Mills | Great films about cricket: The Umpire Strikes Back
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
he interests
of consistency, checksums are disabled.
Hugo.
--
Hugo Mills | Nothing wrong with being written in Perl... Some of
hugo@... carfax.org.uk | my best friends are written in Perl.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
ed data: if drive
> is non-rotational, then prefer reads from it? Or it simply schedules
> the read to the drive that performs faster (irrelative to rotational
> status)?
No, it'll read arbitrarily from the available devices at the moment.
Hugo.
--
Hugo Mills | Pe
in, and whether
zeroing the log might actually hurt the recovery process.
Hugo.
--
Hugo Mills | There's an infinite number of monkeys outside who
hugo@... carfax.org.uk | want to talk to us about this new script for Hamlet
http://carfax.org.uk/ | they've worked out!
PGP: E2AB1DE
e to
> any further attempt at recovery, because the data is by definition either
> backed up, or of such low value that a backup was considered too
> expensive to do, meaning there's a very real possibility of spending more
> time in a recovery attempt that's iffy at best, than the
file's location will have changed. This is the
same reason that btrfs doesn't support swap files (although I don't
know if swapon uses FIEMAP directly, or if there's just some
equivalent mechanism to get the blocks).
Hugo.
--
Hugo Mills | Have found Lost City of Atlantis. High Priest
ng to do git merge, I guess).
>
> Has anyone come across this situation and evolved any policies to handle it?
You can't currently do this efficiently with send/receive. It
should be possible, but it needs a change to the send stream format.
Hugo.
--
Hugo Mills | UNIX: Britis
On Fri, Oct 09, 2015 at 12:16:43AM +0200, Pavel Pisa wrote:
> Hello Hugo,
>
> On Thursday 08 of October 2015 23:13:52 Hugo Mills wrote:
> > On Thu, Oct 08, 2015 at 07:47:33AM -0400, Austin S Hemmelgarn wrote:
> > > On 2015-10-08 04:28, Pavel Pisa wrote:
> > > >
r the delay, I wrote this earlier, but had trouble sending it)
> It is theoretically possible to wipe the FS signature on the out-of
> sync drive, run a device scan, then run 'replace missing' pointing
> at the now 'blank' device, although going that route is really
> risky.
>
, PSU, or CPU would be manifesting
> with many more issues than just this.
> 3. A disk failure would mean that two different disks, from
> different manufacturing lots, are encountering errors on exactly the
> same LBA's at exactly the same time, which while possible is
> a
w to force data recompression?
btrfs fi defrag -c
Hugo.
--
Hugo Mills | A cross? Oy vey, have you picked the wrong vampire!
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
that time though) and mounted it just fine with the
> LABEL only, so it might be something with RAID5.
>
> Anyway it's working now with just a much longer fstab line ;)
>
> Cheers,
> Sjoerd
>
--
Hugo Mills | Vote early, vote often
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
by having one (for RAID-0) or up to three (for
RAID-10) devices with more space left than the rest.
Hugo.
--
Hugo Mills | Dullest spy film ever: The Eastbourne Ultimatum
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 | The Thick of It
signature.asc
Description: Digital signature
> diff --git a/tests/generic/110.out b/tests/generic/110.out
> new file mode 100644
> index 000..64049da
> --- /dev/null
> +++ b/tests/generic/110.out
> @@ -0,0 +1,3 @@
> +QA output created by 110
> +wrote 66560/66560 bytes at offset 0
> +XXX Bytes, X ops; XX:XX:
On Tue, Sep 29, 2015 at 06:13:37PM +0800, Qu Wenruo wrote:
>
>
> 在 2015年09月29日 18:00, Hugo Mills 写道:
> >On Tue, Sep 29, 2015 at 05:34:24PM +0800, Qu Wenruo wrote:
> >>Normally, a bull fallocate call on a fully written and synced file
> >>should not add an
ke this on one
> machine:
>
> [ 256MB ][ 512 MB ][ 256MB ]
>
> And like this on the other:
> [ 512MB ][ 512MB ]
>
> Since the checksums are per block, and the blocks can be different
> arrangements on different machines, they're not
et, which
should then show up in btfs fi show, and allow you to keep using the
FS.
Hugo.
--
Hugo Mills | If you see something, say nothing and drink to
hugo@... carfax.org.uk | forget
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Welcome to Night Vale
signature.asc
Description: Digital signature
ing the latest stable, and things have
improved quite a bit. :)
Hugo.
--
Hugo Mills | For months now, we have been making triumphant
hugo@... carfax.org.uk | retreats before a demoralised enemy who is advancing
http://carfax.org.uk/ | in utter di
> Yes, I have bad ram. I ran memtest and memory is really bad.
> >
> > So a must buy new memory first.
> >
> > Thank you.
> >
> > Frantisek
> >
> > 2015-09-23 16:43 GMT+02:00 Hugo Mills <h...@carfax.org.uk>:
> >> On Wed, Sep 23, 2
- the 4.3.x (mainline)?
>
> Stable sounds more stable to me(hence the name ;) ), but the mainline kernel
> seems to be in more active development?
I'd suggest sticking to the 4.2 series for now. 4.3 will be in
pre-release state for another couple of months (give or take).
201 - 300 of 1315 matches
Mail list logo
