All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: o1bigtenor <o1bigtenor@gmail.com>
Cc: Brad Campbell <lists2009@fnarfbargle.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Advice requested re: hard drive setup for RAID arrays
Date: Wed, 4 Nov 2015 10:05:00 -0500	[thread overview]
Message-ID: <563A1E9C.4060003@turmel.org> (raw)
In-Reply-To: <CAPpdf59BqCABOw=gHw=y8zO-xVzFDn30FLbgqFDjmiBzrgAaHA@mail.gmail.com>

On 11/04/2015 09:30 AM, o1bigtenor wrote:

> I used to have to mount my raid array on every reboot so I can handle running
> the script every reboot. They happen at most weekly and for sure biweekly
> because Firefox doesn't know how to use AND release RAM.

Put an entry in fstab to mount your array at boot.  Put Brad's script in
/etc/rc.local.  Try "man fstab".

You don't need to reboot to clean up after Firefox.  At most, logout and
re-login will do.  Or just "killall firefox".

> Those are the drives Brad uses.

No. The script is generic.  It attempts to fix anyone's drives.  Clearly
falls down on your USB drives.  Oh, well.  Specify the drives you want
instead of using a wildcard.

> I read the files listed.
> There wasn't anything specific as to what to look for.

The following was in your reading list.  The options A-D at the end
couldn't be more clear.

http://marc.info/?l=linux-raid&m=135811522817345&w=1

> There is a lot of traffic which isn't really of interest as I hope that I don't
> have to develop kernel skills. Was hoping to just occasionally browse
> something that would be of interest.

This list is mostly administration skills.  You need those if you are
going to be running raid arrays.  I'm sorry if *reading* inconveniences
you, but the whining won't change anything.  Except to make me less
enthusiastic about helping you.

Phil

  reply	other threads:[~2015-11-04 15:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 12:02 Advice requested re: hard drive setup for RAID arrays o1bigtenor
2015-11-04 13:13 ` Phil Turmel
2015-11-04 14:30   ` o1bigtenor
2015-11-04 15:05     ` Phil Turmel [this message]
     [not found]       ` <CAPpdf5_-3TOiCKq_dDTYGPcJMeEDMRD+xTAjkm-enmCnZPdtzg@mail.gmail.com>
2015-11-04 16:43         ` Phil Turmel
2015-11-04 17:27           ` Rudy Zijlstra
2015-11-05  6:02     ` Brad Campbell
2015-11-04 19:36   ` Edward Kuns
2015-11-04 19:42     ` Wols Lists
2015-11-04 20:09     ` Phil Turmel

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=563A1E9C.4060003@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    --cc=o1bigtenor@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.