From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Understanding DF, etc.
Date: 15 May 2011 19:28:00 +0200 [thread overview]
Message-ID: <BlvXUBvD1uB@helmut.hullen.de> (raw)
In-Reply-To: <20110515170352.GA8927@carfax.org.uk>
Hallo, Hugo,
Du meintest am 15.05.11:
>>>>> # btrfs fi df /
>>>>> Data: total=3D74.01GB, used=3D72.77GB
>>>>> System, DUP: total=3D8.00MB, used=3D16.00KB
>>>>> System: total=3D4.00MB, used=3D0.00
>>>>> Metadata, DUP: total=3D1.75GB, used=3D657.48MB
>>>>> Metadata: total=3D8.00MB, used=3D0.00
>> I don't know what's the meaning of the type "DUP" (instead of
>> "RAID0" or "RAID1" in my example).
> DUP is a form of RAID-1 for single disks. Like RAID-1, it stores
> two copies of the data, but where RAID-1 guarantees that the two
> copies will be on different devices, DUP stores both copies on the
> same device. btrfs uses DUP by default for metadata on single-device
> filesystems, so that if part of the FS metadata is damaged (by, say,
> unrecoverable bad blocks), there's still a good copy.
> If you add another disk to the filesystem and balance, the DUP
> chunks are automatically converted to RAID-1.
Sounds very interesting!
In this special case: does that mean that
> root@tethys:~# df -t btrfs
> Sys. de fichiers 1K-blocs Utilis=E9 Dispo. Uti% Mont=E9
> sur /dev/mapper/VG1-TETHYS
> 152735744 78383976 71999272 53% /
> /dev/mapper/VG1-TETHYS
> 152735744 78383976 71999272 53% /tmp
shows that that device with brutto 150 GByte is nearly full with its 78=
=20
GByte (or 73 GByte) data because it uses this kind of RAID1?
Viele Gruesse!
Helmut
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2011-05-15 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110515170352.GA8927@carfax.org.uk>
2011-05-15 17:28 ` Helmut Hullen [this message]
2011-05-15 17:48 ` Understanding DF, etc Swâmi Petaramesh
2011-05-13 10:53 Swâmi Petaramesh
2011-05-13 19:50 ` Helmut Hullen
2011-05-14 8:01 ` Swâmi Petaramesh
2011-05-15 16:48 ` Helmut Hullen
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=BlvXUBvD1uB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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).