| To: | Annius Groenink <avg@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Mounting real-time device - can it be done? |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | Tue, 13 Feb 2001 18:03:36 -0600 |
| Cc: | Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | Message from Annius Groenink <avg@xxxxxxxxxxxx> of "Wed, 14 Feb 2001 00:57:04 +0100." <Pine.LNX.4.20.0102140056470.5197-100000@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
>
> > Annius Groenink writes:
> > => Unfortunately, this still gives me:
> > =>
> > => iep:/usr/include/linux# mount -t xfs -o rtdev=/dev/hdb3 /dev/hdb4 /mnt/
> xfs
> > => mount: wrong fs type, bad option, bad superblock on /dev/hdb4,
> > => or too many mounted file systems
> > =>
> >
> > Oh yeah - check the syslog output too - the message from mount is
> > useless, but the syslog can be quite informative.
>
>
> Did that. Nothing. Anything I can do to make it more verbose?
>
Dumb question, but do you have xfs in the kernel? Have you successfully
mounted a simple filesystem without a realtime subvolume?
cat /proc/filesystems
nodev sockfs
nodev shm
nodev pipefs
nodev proc
ext2
xfs
nodev devpts
nodev autofs
nodev nfs
If you build xfs as a module, try doing a modprobe xfs and see what it
reports.
Steve
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: less data lost, more fs corruption, Steve Lord |
|---|---|
| Next by Date: | Re: less data lost, more fs corruption, utz lehmann |
| Previous by Thread: | Re: Mounting real-time device - can it be done?, Annius Groenink |
| Next by Thread: | Re: Mounting real-time device - can it be done?, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |