From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org,
"haveaniceday@cv-sv.de" <haveaniceday@cv-sv.de>
Cc: Anand Jain <Anand.Jain@oracle.com>
Subject: Re: btrfsck crashes
Date: Sun, 15 Jul 2012 16:05:00 +0200 [thread overview]
Message-ID: <201207151605.01189.Martin@lichtvoll.de> (raw)
In-Reply-To: <209200388.295540.1341995780489.JavaMail.open-xchange@email.1und1.de>
Am Mittwoch, 11. Juli 2012 schrieb haveaniceday@cv-sv.de:
> PS: I would bet that my kind of usage is a very good stress test for
> btrfs.
>
> - large file system "/backup" btrfs with compress enabled.
>
> Content of the file system:
> - ./server1 .... /server5 as directories
> - for each server the directory has a structure like this:
> backup-YYYY-DD-MM-HH:M
> New backups are created with:
> rsync -axvH --link-dest=/backup/server'n'/backup-...(old, last dir)..
> server:/ /backup/server'n'/backup-YYY-.../.
>
> This generates files with a large number of hard links.
I am using
btrfs subvolume snapshot -r
after a rsync backup for exact this case.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2012-07-15 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 16:08 btrfsck crashes Christian Volkmann
2012-07-09 3:40 ` Anand Jain
2012-07-09 21:23 ` Christian Volkmann
2012-07-10 6:30 ` Anand Jain
2012-07-10 9:13 ` haveaniceday
2012-07-10 11:08 ` haveaniceday
2012-07-11 7:13 ` Anand Jain
2012-07-11 8:36 ` haveaniceday
2012-07-15 14:05 ` Martin Steigerwald [this message]
2012-07-12 19:08 ` Christian Volkmann
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=201207151605.01189.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=Anand.Jain@oracle.com \
--cc=haveaniceday@cv-sv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.