Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I created a fuse mountpoint. After mounting, the file permissions are all screwed up and it says I cannot ls or cd. Permission denied.
The file permissions look like this:
d????????? ? ? ? ? ? temp
and when i list the mounted devices I get:
/dev/fuse on /temp type fuse (rw,nosuid,nodev)
I used mono-fuse. I just created a new folder with permissions 777 and then did a mount. After unmounting I can do all operations, but when I mount, I get such error.
I used
HelloFS.exe that comes along with mono fuse for testing.
Can someone shed some light on this weird behavior and what mistake i have done.
I expect there is an incompatiblity with the userspace fuse library you're using and the kernel fuse version. This results in the kernel not understanding responses and it returning and EIO for everything (including the stat calls that "ls" does).
You should try increasing the debug level. As it's a Mono / CLR application, ensure that the libraries are of an appropriate version for your kernel; you may not need to recompile it.
You should also note that when you mount a directory, the mount-point's original permissions are ignore (and hence need not be 0777) ; the root directory of the new filesystem takes its place.
(You should probably not mount such a filesystem in /temp either; it is an example not for temp files)
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 days ago.
Improve this question
I've mounted an SSD to /mnt/SATA-SSD which has a single exfat partition.
I'd like to make the permissions for the mount point "drwxrwxrwx" but no matter what I try, the permissions wont change from "drwxr-xr-x".
I tried going into the terminal and doing "sudo chmod 777 /mnt/SATA-SSD" which resulted in the permissions remaining at "drwxr-xr-x". I've also tried the same command as root.
I also tried in Dolphin to change the permissions and the write permissions were greyed out.
I'm using Kubuntu 22.10.
It's a drive full of data so I don't really want to reformat it.
I've mounted a few other drives (1. NTFS HDD 2. NTFS SSD 3. NTFS External SSD) in the same way and they don't seem to have this issue. I cant imagine the file format is the issue but at this point I have no idea.
I'm kind of at a loss for how this isn't working. Is there a way to force the permissions to change that's more forceful than chmod or could there some other reason why chmod isn't changing the permissions?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 months ago.
Improve this question
There are some directories that the root user cannot access due to Permission denied.
root#lyria:~# ls -l /disk/ssd14tb/haoki/.cache/ | grep gvfs
ls: cannot access '/disk/ssd14tb/haoki/.cache/gvfs': Permission denied
d????????? ? ? ? ? ? gvfs
This directory is accessible for the owner, though.
haoki#lyria:~$ ls -l /disk/ssd14tb/haoki/.cache/ | grep gvfs
dr-x------ 2 haoki haoki 0 May 15 11:51 gvfs
How to make these folders available for the root user?
I appreciate any help you can provide.
It seems those files are part of a sort of mount made by/for haoki user. Check on this:
The administrator cannot access these files and folders due to how the GNOME Virtual File System works. GVFS is used as a mounting point for some resources such as SFTP and SMB which is established by using FUSE to allow non-privileged users to create their own virtual file systems to access these resources.
Since this filesystem driver is running as a non-privileged user and not as a system kernel with privileged access, filesystems created by FUSE are only accessible to the user using that driver which helps avoid possible complications and as a result, root user access to these files and folders is restricted.
From:
https://support.magnetforensics.com/s/article/Unable-to-view-or-download-some-items-from-Linux-computers
There's a solution to try there as well. But it recommends getting the files from this ?mountpoint? instsead.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I am trying Linux UBUNTU on my windows system. I am knew in Linux UBUNTU.but I don't know that where I can find my files that were on windows 10.
In case you mean WSL Ubuntu:
Your Harddrives are mounted under /mnt/. I like to create a symbolic links to them in my home folder. The should be named like so:
/mnt/c # your C:\ drive
/mnt/s # your S:\ drive
...
In case you mean a Linux livesystem:
If you use a system with a graphical user interface, somewhere in your filemanager you should see the respective drive. Click on it and it should auto-mount. Afterwards you should be able to access your files just as you would expect via the filemanager.
In case you're in terminal mode (= you do not have any graphical user interface), things might get a little strange from a beginner's perspective. In this case I would recommend that you make yourself familiar with the rough structure of the linux filesystem and the commands mount, umount and sudo. Generaly said you will have to do the same thing your filemanager does for you. You mount the drive somewhere in the filesystem tree and then access the folder:
mount /dev/<drive> <directory> # mount your drive into the fs tree
cd <directory> # switch to that folder
ls # should display your drive's content
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I am a newbie to mount. From what I know, the root file / is automatically mounted to /dev/xvda1 or /dev/sda1. In some of the tutorials, people mount file like /dummy to /dev/xvdb1, I don't understand what the meaning of doing this. Because it's parent root file / has already mounted. Could someone explain this to me?
Thanks in advance.
To throw out a very non-exclusive list of possibilities:
Sometimes / doesn't have the capacity for what you intend to use it for, so you want to use a filesystem located on a different physical device for extra storage.
Sometimes you want to mount content from a filesystem that isn't capable of being used as root -- for instance, a FAT or NTFS filesystem, which doesn't properly support UNIX semantics.
Sometimes your other block device is removable, and you're mounting it only temporarily.
Sometimes your other block device is located on media that isn't available at boot time -- requiring iSCSI setup or other operations that prevent it from being used as root without initrd / initramfs facilities your operating system doesn't provide.
Sometimes you want to use a different filesystem with different semantics -- for instance, maybe your xvdb1 is a GFS shared-block filesystem that other machines also have mounted at the same time for combined storage.
Sometimes you have a read-only block device with bulk contents that can't change, and you're mounting it to multiple VMs, vs systems having their own local read-write storage.
The number of possibilities is nearly endless.
This isn't a software development question, and doesn't belong on StackOverflow.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Why initramfs is needed in OS, why we can not mount the root filesystem without this file?
Why we can not mount root fileststem directly, but we need some intermediator (intramfs)?
And how to mount file system from kernel level (kernel side)?
To answer your question, you need to understand, boot process, & how the operating system determines and understands the root fs (which stores the config,bins,data,etc for the rest of the services that come up, when the system is up), the drivers required for talking to the hardware (ex: the storage device or hard disk). Therefore you need to bundle up at least the basic required modules (like file-system and device drivers etc) in your initramfs, to bring up the system and mount the root fs. This is also a duplicate of Is it possible to boot the Linux kernel without creating an initrd image?