From: Mark Ruijter <mruijter@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Data deduplication for Linux : lessfs
Date: Wed, 24 Jun 2009 21:25:56 +0200 [thread overview]
Message-ID: <4A427DC4.7050805@gmail.com> (raw)
In-Reply-To: <BE6893A3-3CF3-4B26-B23D-3951C1BF5034@karlsbakk.net>
[-- Attachment #1: Type: text/plain, Size: 2578 bytes --]
Hi Roy,
>
> It's a good idea, but given the current traffic on the lessfs mailing
> list, I'm not sure if much work is done. I have been a member of that
> list since June 1 and haven't received more than one message, which
> was the one I wrote myself.
>
Almost all the traffic is on the forum - open discussion.
Only one person posted to the mailing list. ;-)
> If done smartly, this may perhaps be possible, but the problem is the
> filesystem's metadata. Is this going to be dedup'ed? How much will
> this take? A simple backup will update atime on all the files backed
> up, and although atime isn't always wanted or needed, the problem
> occurs elsewhere.
Typically the meta data on production systems is approx 10%~20% of the
deduplicated stored data.
Stored data is on my systems 40x less then the data written to the
filesystem.
For example, from a real life backup server making dozens of backups
each day:
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/cciss/c0d0p3 9.7G 2.4G 6.9G 26% /
/dev/cciss/c0d0p1 99M 23M 72M 24% /boot
tmpfs 7.9G 0 7.9G 0% /dev/shm
/dev/cciss/c0d0p4 246G 6.0G 241G 3% /meta
/dev/cciss/c0d1p1 274G 73G 202G 27% /blockdata
/dev/cciss/c1d0p1 4.1T 1.5T 2.7T 35% /data
lessfs 4.1T 1.5T 2.7T 35% /pooldata
[root@lessfssrv pooldata]# du . -s -h
31T .
[root@lessfssrv pooldata]# ls -alh /data/current/
total 314G
drwxr-xr-x 2 root root 26 Jun 1 00:12 .
drwxr-xr-x 6 root root 59 Jun 1 00:12 ..
-rw-r--r-- 1 root root 314G Jun 22 14:26 blockdata.tch
[root@lessfssrv pooldata]# ls -alh /meta/current/
total 1.4G
drwxr-xr-x 2 root root 63 Jun 1 00:12 .
drwxr-xr-x 6 root root 59 Jun 1 00:12 ..
-rw-r--r-- 1 root root 1.3G Jun 22 14:52 blockusage.tch
-rw-r--r-- 1 root root 89M Jun 22 14:45 dirent.tcb
-rw-r--r-- 1 root root 89M Jun 22 14:52 metadata.tcb
Mark.
>
>
> roy
> --
> Roy Sigurd Karlsbakk
> (+47) 97542685
> roy@karlsbakk.net
> http://blogg.karlsbakk.net/
> --
> I all pedagogikk er det essensielt at pensum presenteres
> intelligibelt. Det er et element�rt imperativ for alle pedagoger �
> unng� eksessiv anvendelse av idiomer med fremmed opprinnelse. I de
> fleste tilfeller eksisterer adekvate og relevante synonymer p� norsk.
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
[-- Attachment #2: Type: text/html, Size: 4239 bytes --]
next prev parent reply other threads:[~2009-06-24 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 15:12 [linux-lvm] Data deduplication for Linux : lessfs Mark Ruijter
2009-06-24 18:50 ` Roy Sigurd Karlsbakk
2009-06-24 19:25 ` Mark Ruijter [this message]
2009-06-24 19:43 ` Roy Sigurd Karlsbakk
2009-06-24 19:32 ` Greg Freemyer
2009-06-24 20:04 ` Les Mikesell
2009-06-24 20:09 ` Roy Sigurd Karlsbakk
2009-06-24 20:59 ` Les Mikesell
2009-06-24 21:03 ` malahal
2009-06-24 21:21 ` Les Mikesell
2009-06-24 20:12 ` Mark Ruijter
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=4A427DC4.7050805@gmail.com \
--to=mruijter@gmail.com \
--cc=linux-lvm@redhat.com \
/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).