From: Hugo Mills <hugo@carfax.org.uk>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfsck does not fix
Date: Tue, 14 Jan 2014 09:38:08 +0000 [thread overview]
Message-ID: <20140114093808.GD7221@carfax.org.uk> (raw)
In-Reply-To: <pan$8a0dd$9f46c908$89053e7c$efd0a239@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
On Tue, Jan 14, 2014 at 09:30:14AM +0000, Duncan wrote:
> Chris Murphy posted on Tue, 14 Jan 2014 00:49:13 -0700 as excerpted:
>
> > On Jan 13, 2014, at 11:03 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> >
> >> Chris Murphy posted on Mon, 13 Jan 2014 17:40:33 -0700 as excerpted:
> >>
> >>> btrfs-image -c 9-t 4 /dev/sdX /mnt/<pathtoanothervolume+filename>
> >>>
> >>> You can keep it handy in case a dev asks for it or you can attach it
> >>> to a kernel.org bug report.
> >>
> >> How big are they? manpage says it's metadata only (data is zeroed),
> >> so I'd guess one could expect it to be about metadata size as reported
> >> by btrfs fi df?
> >
> > # btrfs fi df /mnt/isos
> > Metadata, DUP: total=1.00GiB, used=289.53MiB
> >
> > 193M -rw-r--r--. 1 root root 193M Jan 14 00:44 sdb.img
> >
> > Guess that's too big to attach to a bugzilla bug.
>
> ~ 290 MiB metadata, ~ 190 MiB btrfs-image. So roughly 2/3 the size of
> metadata. Metadata minus file tails (which are actually data, thus
> should be zeroed)?
>
> Thanks.
>
> I wonder if it compresses?
Yes, that's the -c9 option, and it compresses fairly well.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Questions are a burden, and answers a prison for oneself. ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-01-14 9:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 19:41 btrfsck does not fix Hendrik Friedel
2014-01-03 23:33 ` Chris Murphy
2014-01-04 21:21 ` Hendrik Friedel
2014-01-05 13:36 ` Hendrik Friedel
2014-01-05 16:55 ` Chris Murphy
2014-01-07 20:38 ` Hendrik Friedel
2014-01-10 23:53 ` Hendrik Friedel
2014-01-11 1:05 ` Chris Murphy
2014-01-12 22:31 ` Hendrik Friedel
2014-01-14 0:40 ` Chris Murphy
2014-01-14 6:03 ` Duncan
2014-01-14 7:49 ` Chris Murphy
2014-01-14 9:30 ` Duncan
2014-01-14 9:38 ` Hugo Mills [this message]
2014-01-14 17:17 ` Chris Murphy
2014-01-18 7:20 ` Chris Samuel
2014-01-14 8:16 ` Hugo Mills
2014-01-19 19:37 ` Martin Steigerwald
2014-01-21 20:00 ` Hendrik Friedel
2014-01-21 20:01 ` Hendrik Friedel
2014-02-08 22:01 ` Hendrik Friedel
2014-02-09 0:45 ` Chris Murphy
2014-02-09 8:36 ` Hendrik Friedel
2014-02-11 1:45 ` Chris Murphy
2014-02-11 2:23 ` Chris Murphy
2014-02-16 19:18 ` Hendrik Friedel
2014-02-16 19:54 ` Chris Murphy
2014-02-17 3:20 ` Duncan
2014-02-17 9:41 ` Goswin von Brederlow
2014-02-18 21:55 ` Hendrik Friedel
2014-02-18 22:12 ` Chris Murphy
2014-03-02 18:39 ` Hendrik Friedel
2014-03-03 22:35 ` Chris Murphy
2014-03-04 6:42 ` Hendrik Friedel
2014-03-04 17:02 ` Chris Murphy
2014-03-03 1:09 ` Russell Coker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140114093808.GD7221@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).