[Top] [All Lists]

Re: Pid: 8345, comm: rsync Not tainted #1

To: xfs@xxxxxxxxxxx
Subject: Re: Pid: 8345, comm: rsync Not tainted #1
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 27 Oct 2010 12:58:45 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>
In-reply-to: <20101027035548.GD32255@dastard>
Organization: it-management http://it-management.at
References: <4CC67450.9020602@xxxxxxxxxxxx> <201010270124.44846@xxxxxx> <20101027035548.GD32255@dastard>
User-agent: KMail/1.13.5 (Linux/; KDE/4.4.4; x86_64; ; )
On Mittwoch, 27. Oktober 2010 Dave Chinner wrote:
> I'd suggest that people learn how to tweak udev hotplug rules so
> that when the device is first created (i.e. during hotplug) the
> scheduler, queue depth and readahead are set automatically. That way
> you don't have to rely on devices being discovered before your script
> runs...
> Another benefit of doing it this way is that it is easy to set
> default rules for different types of devices based on regex matching
> e.g. different configs for "sd*" vs "dm*" vs "vd*" are trivial to
> set up.

Sounds very nice. But the script I use will still work when upgrading 
the server from openSUSE 11.2 to 11.3, and is therefore the preferred 
choice for me.

Also, I'd need to find information and learn how to tweak udev hotplug 
rules. I want to implement this on about 30 VMs on 2 different hosts, 
with 3 different release states of servers (openSUSE 11.1, 11.2 and 
11.3). The chance is high that I'd need two or three different udev 
tweaks for the different releases, so I don't see the benefit of udev 
for me. I wrote the script in about the same time I wrote this mail.

That's always the problem between developers ("ah, cool new stuff") and 
admins ("i need this on 500 servers with least possible work for me, and 
it must still work after any updates/upgrades").

mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31

****** Radiointerview zum Thema Spam ******

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/

Attachment: signature.asc
Description: This is a digitally signed message part.

<Prev in Thread] Current Thread [Next in Thread>