From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] HUGE LVM log file...
Date: Wed, 18 Jul 2001 16:55:28 +0200 [thread overview]
Message-ID: <20010718165528.B24438@sistina.com> (raw)
In-Reply-To: <20010717232842.A6067@tiger.bigcats.invalid>; from weissel@netcologne.de on Tue, Jul 17, 2001 at 11:28:42PM +0200
On Tue, Jul 17, 2001 at 11:28:42PM +0200, Wolfgang Weisselberg wrote:
> Guennadi Liakhovetski (g.liakhovetski@ragingbull.com) wrote 23 lines:
>
> > > > My /var/log/lvm has grown up to 800MB+... and has filled up the disk...
>
> > > lvmsadc is probably filling it run by cron.
>
> > Thanks! But why / what for is it needed and why is it created by default
>
> man lvmsadc:
> lvmsadc collects the read/write statistics of the logical
> volume manager to the file "LogFilePath" or to stdout if
> no LogFilePath is given. You should create a cron entry
> for lvmsadc which runs it at regular intervals eg. 10 min�
> utes.
Well, it should rather say: "If you want to have I/O statistics at hand
for performance tuning, you could create a cron entry..."
Will change that.
>
> That statistical info can be later used to e.g. decide which
> LEs shoud have PEs at the faster 'begin' (outer edge) of the
> HD. An automatic LE mover program has not been written yet.
Well, it depends on the brand/model, if the outer edge is the fast area :-)
>
> -Wolfgang
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-07-18 14:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 11:13 [linux-lvm] HUGE LVM log file Guennadi Liakhovetski
2001-07-17 11:14 ` Heinz J. Mauelshagen
2001-07-17 11:28 ` Guennadi Liakhovetski
2001-07-17 11:28 ` Heinz J. Mauelshagen
2001-07-17 21:28 ` Wolfgang Weisselberg
2001-07-18 14:55 ` Heinz J. Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-17 21:52 Gonyou, Austin
2001-07-18 0:00 ` Wolfgang Weisselberg
2001-07-18 8:22 ` Joe Thornber
2001-07-18 8:48 ` Benoit SERRA
2001-07-18 9:33 ` Joe Thornber
2001-07-18 19:23 ` Ragnar Kjørstad
2001-07-18 22:22 ` lembark
2001-07-18 9:46 ` Adam Cioccarelli
[not found] ` <Pine.LNX.4.33.0107181141480.25686-100000@vie-ac.office.ece tra.com>
2001-07-18 9:47 ` Benoit SERRA
2001-07-18 13:29 ` Iain Campbell
2001-07-18 17:02 ` Steven Lembark
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=20010718165528.B24438@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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