What would stop a filesystem name???

What would stop a filesystem name???

Post by Ted Sudte » Mon, 09 Nov 1998 04:00:00



Sorry for the cross posting, but 4 weeks is enough of this...

I cannot mount any more file systems.  I have 5 mounted now. They are
/, /usr, /usr/local, /data1, /data2.  I have good devices that I can
mount /data1 or 2 on, but not /data3 or any other name.  What is going
on??? (or what have I done)  What controls this?
I can unmount one or two systems, but cannot mount  any name other
than the above.
Using 'mount -t ext2 /devices  /filesystem name'
Please help

Ted
\\\\\\\\\\\\\\\\\\\\
NorthStar Technoliges
Ted Sudtell
/////////////////////

 
 
 

What would stop a filesystem name???

Post by Jay » Mon, 09 Nov 1998 04:00:00


it seems that you need to modify you /etc/fstab file. just put the
partitions you
want to mount. when you try to mount
just use "mount  /dev/hda?". you do not need to specify the file system
name
every single time. also check "man mount" to learn how it works.

> Sorry for the cross posting, but 4 weeks is enough of this...

> I cannot mount any more file systems.  I have 5 mounted now. They are
> /, /usr, /usr/local, /data1, /data2.  I have good devices that I can
> mount /data1 or 2 on, but not /data3 or any other name.  What is going
> on??? (or what have I done)  What controls this?
> I can unmount one or two systems, but cannot mount  any name other
> than the above.
> Using 'mount -t ext2 /devices  /filesystem name'
> Please help

> Ted
> \\\\\\\\\\\\\\\\\\\\
> NorthStar Technoliges
> Ted Sudtell
> /////////////////////


 
 
 

What would stop a filesystem name???

Post by James Youngm » Mon, 09 Nov 1998 04:00:00



> Sorry for the cross posting, but 4 weeks is enough of this...

> I cannot mount any more file systems.  I have 5 mounted now. They are
> /, /usr, /usr/local, /data1, /data2.  I have good devices that I can
> mount /data1 or 2 on, but not /data3 or any other name.  What is going
> on??? (or what have I done)  What controls this?
> I can unmount one or two systems, but cannot mount  any name other
> than the above.
> Using 'mount -t ext2 /devices  /filesystem name'
> Please help

Your plea for help is COMPLETELY in vain unless you state exactly what
command you typed, what you expected to happen, what did happen, and
the error message you got.

--

 
 
 

What would stop a filesystem name???

Post by Ted Sudte » Mon, 09 Nov 1998 04:00:00


Jay, I have been adding and changing fstab.  Turns out I have to have
a real directory off of / in order to mount.  Take a look at you / and
see if all your mounted file systems are not there.  If not please let
me know.


>it seems that you need to modify you /etc/fstab file. just put the
>partitions you
>want to mount. when you try to mount
>just use "mount  /dev/hda?". you do not need to specify the file system
>name
>every single time. also check "man mount" to learn how it works.


>> Sorry for the cross posting, but 4 weeks is enough of this...

>> I cannot mount any more file systems.  I have 5 mounted now. They are
>> /, /usr, /usr/local, /data1, /data2.  I have good devices that I can

\\\\\\\\\\\\\\\\\\\\
NorthStar Technoliges
Ted Sudtell
/////////////////////
 
 
 

What would stop a filesystem name???

Post by Ted Sudte » Mon, 09 Nov 1998 04:00:00


The only thing I left out was the error message. I did have it in the
other postings.  If I can mount and umount (mke2fs must work), have
good devices (fdisk must work right) and, below, the mount command I
used, what is left? BTW the error was 'mount point does not exist'.
I found out this AM that if I actually mkdir (filesystemName) off of
/, that it will mount.  I find it hard to beleave that if I add a new
HD to my existing system, I manualy have to add the new filesystem
names off of / .  After using fdisk, mke2fs, change the fstab file and
use the mount command.  There must be another answer.
Thanks for taking the time to comment.
ts

On 08 Nov 1998 12:09:28 +0000,



>> than the above.
>> Using 'mount -t ext2 /devices  /filesystem name'
>> Please help

>Your plea for help is COMPLETELY in vain unless you state exactly what
>command you typed, what you expected to happen, what did happen, and
>the error message you got.

>--


\\\\\\\\\\\\\\\\\\\\
NorthStar Technoliges
Ted Sudtell
/////////////////////
 
 
 

What would stop a filesystem name???

Post by david kahan » Mon, 09 Nov 1998 04:00:00



> I found out this AM that if I actually mkdir (filesystemName) off of
> /, that it will mount.  I find it hard to beleave that if I add a new
> HD to my existing system, I manualy have to add the new filesystem
> names off of / .

Believe it!

Quote:> After using fdisk, mke2fs, change the fstab file and
> use the mount command.  There must be another answer.
> Thanks for taking the time to comment.
> ts

I don't think there is another answer. If you don't create
the mount point by hand, and it doesn't exist already,
there is no way mount can know what you want to do. So it gives
the error: mount point does not exist.

cheers,

- dave k.

 
 
 

What would stop a filesystem name???

Post by Robert Nicho » Tue, 10 Nov 1998 04:00:00



:  I find it hard to beleave that if I add a new
:HD to my existing system, I manualy have to add the new filesystem
:names off of / .  After using fdisk, mke2fs, change the fstab file and
:use the mount command.  There must be another answer.

You've got the sequence slightly wrong, which is perhaps what makes it
so unbelievable.  You have to create the mount point directory some time
_before_ you issue the mount command, not after.  Yes, it would
certainly be possible to change the 'mount' program to create the
directory if it did not already exist, but that's not the way the
'mount' command works in any Un*x system I've ever seen.

--


PGP public key 1024/9A9C7955
Key fingerprint = 2F E5 82 F8 5D 06 A2 59  20 65 44 68 87 EC A7 D7

 
 
 

What would stop a filesystem name???

Post by James Youngm » Wed, 11 Nov 1998 04:00:00



> You've got the sequence slightly wrong, which is perhaps what makes it
> so unbelievable.  You have to create the mount point directory some time
> _before_ you issue the mount command, not after.  Yes, it would
> certainly be possible to change the 'mount' program to create the
> directory if it did not already exist, but that's not the way the
> 'mount' command works in any Un*x system I've ever seen.

If the mount command worked differently in this respect, it would only
change two things that I can think of:-

1. When you unmount the filesystem, should the directory be deleted
again?  Is that always the right thing to do?   I don't think it is.

2. When you are trying to rescue a random system, using a boot disk,
it makes it easier if the mount points already exist.  That is, if you
mount /dev/hda7 on /mnt/hda7 and see

# ls /mnt/hda7
bin         etc         home        tmp         usr
boot        lib         mnt         root        sbin        
dev         export      lost+found  proc        var

It's a bit easier to grok that you're looking at / than if you see
# ls /mnt/hda7
bin         etc         boot        lib         dev        
sbin        proc

Here's a tip:-

# ( cd /mnt/floppy && ln -s nsuchfile "filesystem not mounted" )
# ls /mnt/floppy
filesystem not mounted

..and if you are using colour-ls, it's even coloured!  I find this
usefully distinguishes empty floppies from not-mounted floppies.

--

 
 
 

1. killall -STOP xclock... hangs filesystem

HiHo,

I am using kernel 2.0.33 on a P55C (P166MMX) with something that was a
RedHat 3.0.3 some time ago.

In preperation for playing an animation under X I "killall -STOP"ed the two
xclocks and one xosview running on the machine (this I did as
root)(paranoia mode -- I want smooth playback).

I had no problem with the animation, but then, completely independent, I
tried to copy some file around (as normal user) but got a "file too large"
error. The copy operation left the destination file empty (source was like
3kb and there were still enough bytes free left). I then tried to do a
"echo hallo > ttt", to no avail. A file ttt was created, but left empty
again. The same happened on other partitions...

After completely killing the stopped tasks everything worked as normal
again. I have yet to reprocduce this bug. It is not the first time that I
kill -STOP processes for some reason, but the first time such a strange
behaviour has occured -- at least I can't explain it.

Regards, Colin

--
----

Lehr- und Forschungsgebiet Mathemathische Grundlagen der Informatik
University of Technology Aachen        Ahornstr. 55, D-52074 Aachen
                                                               ----

2. Linux "family tree" & Caldera

3. Quick stop/start Filesystem ?

4. Elsa W2000Pro 32Bit color Problem

5. dump0.3 stopped working for one filesystem since april

6. Dumb Terminals and 8 port card.

7. Stop user seeing rest of filesystem

8. RH 6.0/Banshee/Seeing only 25% of screen...

9. Load stops with VFS: Mounted root (ext2 filesystem) readonly

10. inetd, named, httpd when to start and stop.

11. Named stops after few hours

12. please stop to misusing the gnu name!!