![]() ![]() The mount program tries to guess exactly what could have caused the error code. Your mount command did not print the generic description of the error code: "No such file or directory". I say that the directory technically still exists, because it still has an inode number (and the inode still stores a time stamp, and a permission mode, etc): # ls -l -i -d. : mount(2) system call failed: No such file or directory. Similarly, you are not allowed to mount a filesystem on top of a deleted directory. Mkdir: cannot create directory ‘subdir’: No such file or directory But it fits better than any of the other error codes :-). Technically the error code is confusing, because the directory technically still exists. ![]() The description for this error code is "No such file or directory". When you try to use a deleted directory, Linux returns the error code ENOENT. The reason is that after you delete a directory, you are not allowed to use it as a directory. You are not allowed to run the commands you tried (on Linux). Then you can continue using the /proc filesystem as usual. Probably you only want to run the first three commands above :-). ![]() However you don't say any reason why you want to do that :-). You could avoid the new error message if you run umount /proc/ twice, before trying to mount it again. In that case, the last command will show a new message: mount: /proc: proc already mounted on /proc To avoid this error message, you need to run another command first: root# mkdir /tmp/test & mount -bind /tmp/test/ /proc/īut you probably started with the proc psuedo-filesystem mounted on /proc. ![]()
0 Comments
Leave a Reply. |