linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Joel Gwynn" <joelman@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM drive changed from USB to Firewire
Date: Sun, 5 Mar 2006 15:27:41 -0500	[thread overview]
Message-ID: <1d4c059f0603051227l6ca53c1foae4a7feb0390d6af@mail.gmail.com> (raw)
In-Reply-To: <44033100.6010600@tsss.org>

Thanks.  It turns out that on Debian the hotplug scripts run after the
mount scripts, so I ended up taking the LVM entries out of fstab
altogether and adding a script to do the vgscan, vgchange and mount.

On 2/27/06, kelsey hudson <khudson@tsss.org> wrote:
> David Brown wrote:
> >>The problem is that the drive is not found at boot anymore, and an
> >>error is raised because it can't be mounted. But if I do a vgscan,
> >>then a vgchage -ay, then mount -a, all is well and my volumes are
> >>mounted.
> >>
> >>How do I tell LVM to look at the firewire card instead of the usb controller?
> >
> > LVM should look at all of the devices.
> >
> > Most likely the firewire interface/driver takes longer to startup than the
> > USB does, and the drive isn't visible when the startup scripts do their
> > vgscan.
>
> i've had a bunch of success with one machine on which I run LVM by
> simply adding a 5-second wait period between the time the kernel calls
> /sbin/init and it begins executing the contents of whatever rc script
> init starts at your desired runlevel (add 'sleep 5' to the beginning of
> this script). kernel threads are great in some circumstances (like
> improving boot speed), but sometimes i guess you could say it boots too
> fast for its own good!
>
> just a side note though: my experience with ieee1394 under linux has
> been less-than-satisfactory: i can't seem to get a decent aggregate raw
> transfer rate of >11MByte/sec, no matter what hardware i use. i've since
>   switched back to usb2.0, even though usb is completely and wholly the
> wrong transport to use for mass storage devices :(
>
> if you can get your disks working faster than this, please let me know
> how you did it. :)
>
> thanks
> -kelsey
>
> _______________________________________________
> 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/
>

      reply	other threads:[~2006-03-05 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25 14:59 [linux-lvm] LVM drive changed from USB to Firewire Joel Gwynn
2006-02-25 19:12 ` David Brown
2006-02-27 17:04   ` kelsey hudson
2006-03-05 20:27     ` Joel Gwynn [this message]

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=1d4c059f0603051227l6ca53c1foae4a7feb0390d6af@mail.gmail.com \
    --to=joelman@gmail.com \
    --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).