linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Coulson <david@davidcoulson.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Offline fsck (checking snapshots)
Date: Fri, 09 May 2008 21:07:44 -0400	[thread overview]
Message-ID: <4824F560.208@davidcoulson.net> (raw)
In-Reply-To: <48110C2D.5020800@kadzban.is-a-geek.net>

[-- Attachment #1: Type: text/plain, Size: 2717 bytes --]

I've been playing with this script today - Is there a more current 
version, or someone who maintains it? There are a bunch of things that 
seem to be broken that I ended up cleaning up on my own (e.g. it 
calculates the snapshot size in M, then creates it in extents...).

I imagine there are other users who are frustrated with it, as it does 
not run cleanly as it is.

David

Bryan Kadzban wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> There was some discussion on the ext3-users list a few months ago, about
> how e2fsck took a long time to run, and it was getting forced because it
> keeps track of a couple of counters that can force it (the counters are
> days since the last full fsck, and mounts since the last full fsck).
> (The thread starts at [1], the script development started at [2], and
> the most recent version is at [3].  The one extra thing I've added is
> skipping ext2/3 FSes that have an external journal.)
>
> The suggestion was made that if the user is using LVM, a temporary
> snapshot could be taken, and then fsck could be run on that.  If it
> succeeds, then it's possible to set the last-fsck-time and mount-count
> while the real FS is mounted.
>
> I've gotten a script that I think is reasonable, that handles this.
> With some help from others, it now works with XFS as well as ext2/3, and
> it's supposed to also work with JFS.  Since it requires LVM, I think it
> might make sense to put something like it into the LVM userspace tools.
>
> (There is one issue: it also requires blkid and logsave from e2fsprogs.
> I could work around the requirement for logsave (using tee -a), but
> blkid would be harder.)
>
> The idea behind the script is, you run it at night from cron; it will
> check each LV on the system and mail a user if there are any problems.
> It also logs to syslog.
>
> I've attached the script and its configuration file to this message.
> Comments?
>
> [1] https://www.redhat.com/archives/ext3-users/2008-January/msg00027.html
>
> [2] https://www.redhat.com/archives/ext3-users/2008-January/msg00032.html
>
> [3]
> https://www.redhat.com/archives/ext3-users/2008-February/msg00004.html
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFIEQwpS5vET1Wea5wRA43cAKDWGJVFgV6fmJKeQUgcPH6Ebd1aygCfb4a9
> TbiWVGUYFnPeQSWiJVl0x2k=
> =Juq0
> -----END PGP SIGNATURE-----
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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: 3639 bytes --]

  parent reply	other threads:[~2008-05-10  1:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 22:39 [linux-lvm] Offline fsck (checking snapshots) Bryan Kadzban
2008-04-27  1:26 ` Charles Marcus
2008-04-27  2:17   ` Bryan Kadzban
2008-04-27 19:48     ` Charles Marcus
2008-04-27 23:37       ` Bryan Kadzban
2008-04-27 23:48         ` Dale
2008-05-10  1:07 ` David Coulson [this message]
2008-05-11  0:25   ` Bryan Kadzban

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=4824F560.208@davidcoulson.net \
    --to=david@davidcoulson.net \
    --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).