linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: [RFC] online scrub for ext4
Date: Fri, 21 Jul 2017 17:26:43 -0700	[thread overview]
Message-ID: <20170722002643.GD4211@magnolia> (raw)

Hi all,

On this week's conference call, we discussed polishing e2croncheck into
something resembling a workable package, and I mentioned that some time
ago I'd adapted the script into a more general utility.  I've cleaned up
the scripts somewhat, so we can use them as a basis for discussion.

The first mail contains the base script to create the lvm snapshot, fsck
the snapshot, remove the snapshot, and fstrim the original filesystem.
It also contains a udev script to discourage it from making symlinks in
/dev/disk.

The second mail contains a script to identify eligible lvs containing
ext4 filesystms and call the actual invoker script.

The third mail contains systemd units to manage invocation and
containment of the scripts.

Note that despite my earlier outline, I don't actually have a boot time
script that cleans out any leftover fsck snapshots, though it wouldn't
be difficult to write.

Note also the lack of distro installer/partitioner support -- your ext4
filesystems /must/ be managed by lvm, and you /must/ have at least 256M
free in each volume group.  There's no daemon to watch for snapshots
filling up in order to kill the fsck and snapshot.

--D

             reply	other threads:[~2017-07-22  0:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-22  0:26 Darrick J. Wong [this message]
2017-07-22  0:29 ` [RFC 1/3] scripts to create and fsck a snapshot Darrick J. Wong
2017-07-22  0:30 ` [RFC 2/3] scripts to find eligible lv ext4 filesystems Darrick J. Wong
2017-07-22  0:33 ` [RFC 3/3] systemd integration scripts Darrick J. Wong

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=20170722002643.GD4211@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).