From: Stan Hoeppner <stan@hardwarefreak.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: Julien FERRERO <jferrero06@gmail.com>,
Ric Wheeler <rwheeler@redhat.com>,
xfs@oss.sgi.com
Subject: Re: XFS filesystem corruption
Date: Tue, 12 Mar 2013 17:16:24 -0500 [thread overview]
Message-ID: <513FA938.6080603@hardwarefreak.com> (raw)
In-Reply-To: <201303121142.13980.Martin@lichtvoll.de>
On 3/12/2013 5:42 AM, Martin Steigerwald wrote:
> Am Freitag, 8. März 2013 schrieb Stan Hoeppner:
>> If the techs are determined to hard cut power because they don't have
>> the time or the knowledge to do a clean shutdown, it may be well worth
>> your time/effort to write a script and teach the field techs to execute
>> it, before flipping the master switch. Your simple script would run as
>> root, or you'd need to do some sudo foo within, and would contain
>> something like:
>>
>> #! /bin/sh
>> sync
>> echo 2 > /proc/sys/vm/drop_caches
>> echo "Ready for power down."
>
> mount -o remount,ro /your/mount/point
>
> One can at least try. Maybe some "service stop" commands before that.
>
> But then, if using a script like this, why not just type "halt"?
...
The real solution to the OP's problem has nothing to do with XFS, buffer
flushing, nor Linux shutdown modes. The problem is power and automation
of cutting power. And the solution is rather simple.
Put a small UPS in the van backing the server, connect USB or serial,
and configure upsmon. When the crews hit the master switch, AC to the
UPS is lost, and upsmon then performs a clean shutdown of the server.
The crews do nothing more than they currently do. And they don't have
to wait on anything. If the previously described "master" switch *is*
currently a UPS, simply install another smaller unit inline to the
server. Disable the audible alarm on the small unit as by default it
will screech continuously while AC input is absent. At the end of the
day they simply flip the switch on this little UPS so it's not running
overnight/weekends (though with no load it probably wouldn't drain the
battery--this just a safety precaution). At the start of the next day,
they flip the master switch, then the little UPS switch.
I've not laid eyes on the vans/power circuits/gear in question so I'm
making educated guesses. There may be even better/easier ways to do it.
But one way or another, a properly configured UPS/upsmon setup is the
way to go, if the desire is to easily control everything with power
switches.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-12 22:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 15:08 XFS filesystem corruption Julien FERRERO
2013-03-06 15:15 ` Emmanuel Florac
2013-03-06 16:16 ` Julien FERRERO
2013-03-06 16:47 ` Ric Wheeler
2013-03-06 22:21 ` Emmanuel Florac
2013-03-06 23:12 ` Ric Wheeler
2013-03-07 13:15 ` Julien FERRERO
2013-03-07 13:40 ` Ric Wheeler
2013-03-07 23:22 ` Dave Chinner
2013-03-08 10:16 ` Julien FERRERO
2013-03-12 9:57 ` Martin Steigerwald
2013-03-08 8:39 ` Stan Hoeppner
2013-03-08 10:17 ` Julien FERRERO
2013-03-08 12:20 ` Ric Wheeler
2013-03-08 18:59 ` Stan Hoeppner
2013-03-09 9:11 ` Dave Chinner
2013-03-09 18:51 ` Stan Hoeppner
2013-03-10 22:45 ` Dave Chinner
2013-03-10 23:54 ` Stan Hoeppner
2013-03-11 0:50 ` Dave Chinner
2013-03-11 9:29 ` Stan Hoeppner
2013-03-11 22:45 ` Dave Chinner
2013-03-11 9:25 ` Julien FERRERO
2013-03-12 10:54 ` Emmanuel Florac
2013-03-12 10:42 ` Martin Steigerwald
2013-03-12 22:16 ` Stan Hoeppner [this message]
2013-03-07 3:56 ` Stan Hoeppner
2013-03-07 13:04 ` Julien FERRERO
2013-03-07 13:32 ` Stan Hoeppner
2013-03-10 2:50 ` Eric Sandeen
2013-03-10 22:11 ` Dave Chinner
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=513FA938.6080603@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=Martin@lichtvoll.de \
--cc=jferrero06@gmail.com \
--cc=rwheeler@redhat.com \
--cc=xfs@oss.sgi.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