Tag Info

New answers tagged

0

I have bad news for you: if I'm reading the code in http://lxr.free-electrons.com/source/fs/efs/ correctly, Linux -- even the very newest version -- does not implement write access to EFS, probably because it was believed that the only use for a filesystem that old was to migrate data off of old disks.


1

Is Filesystem the mount point? You could try the mount -o remount,rw -t efs /dev/sdb1 Filesystem option to remount the filesystem as read-write.


0

Figured i might update this with my solution, I just ended up building Openwrt from source, and included the required packages in the build, and now it works fine.


4

To disable the writing of access times, you need to mount the filesystem(s) in question with the noatime option. To mount an already mounted filesystem with the noatime option, do the following: mount /home -o remount,noatime To make the change permanent, update your /etc/fstab and add noatime to the options field. For example. Before: ...


1

Try umount -f /media/sdb1 or umount -l /media/sdb1. If all else fails you can manually edit /etc/mtab to remove the offending mount entry.


1

Solution Add the following entry to your etc/fstab file: # device mountpoint fs-type options dump fsckorder ... ip.ip.ip.ip:/home /mnt nfs rw 0 0 ... Reference The Linux Documentation Project - 4.2. Getting NFS File Systems to Be Mounted at Boot Time


0

Instead of using sudo to grant the possibility to use unshare, you could use the setuid bit, because the unshare program is designed to work with it. It says in the man page: The unshare command drops potential privileges before executing the target program. This allows to setuid unshare. So after executing sudo chmod u+s /usr/bin/unshare, running ...


6

# rm -rf /path/to/undeletable rm: cannot remove ‘/path/to/undeletable’: Is a directory rm calls stat(2) to check whether /path/to/undeletable is a directory (to be deleted by rmdir(2)) or a file (to be deleted by unlink(2). Since the stat call fails (we'll see why in a minute), rm decides to use unlink, which explains the error message. # rmdir ...


4

A BIOS boot partition doesn't contain a filesystem; it's just a place to put some GRUB code that on an MBR disk would've been located immediately after the boot sector, before the start of the first partition. On a GPT disk, that area is used by the (larger) partition table and isn't available for bootloader code, so the bootloader code goes in a small ...


1

disks can be mounted on any directories, there are however pitfall. all disk must be mounted before application (e.g. drupal) is started. "deepest" directories must be mounted last (e.g mount /storage/drupalprivate/ before /storage/drupalprivate/data1 ). any existing file or dir under /storage/drupalprivate/data1 on your SSD disk, will be unavailable/hide ...


0

I have fixed the drive. All I had to do was check the partition with a partition editor and it fixed it. Hopefully this will help others with the same problem.


1

Yes. You can see Showing Only Interesting Mount Points/Filtering Non-Interesting Types or Listing Directories under / that are Not Under the Same Mountpoint for some example usage, but there's also a brief rundown below. The command you are asking about is findmnt (though lsblk might also serve): lsblk -f /dev/sda[12] NAME FSTYPE LABEL UUID ...


3

On Linux, you can now use the findmnt command from util-linux (since version 2.18): $ findmnt -S /dev/VG_SC/home TARGET SOURCE FSTYPE OPTIONS /home /dev/mapper/VG_SC-home ext4 rw,relatime,errors=remount-ro,data=ordered Or lsblk (also from util-linux, since 2.19): $ lsblk /dev/VG_SC/home NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT ...


1

I don't know of a clean and simple way to detect whether or not a device node in /dev is mounted. This is what I can offer, though. It handles directly mounted devices (/dev/sda1) and devices mounted by UUID (/dev/disk/by-uuid/aa4e7b08-6547-4b5a-85ad-094e9e1af74f). It breaks if your device names contain whitespace. deviceIsMounted() { local DEVICE="$1" ...


-1

Just run the below command: df -h


1

Are you using a cluster environment? If yes, please check if the device has been using by another node. Also please make sure /dev/sda2 has a correct format. The "df" command only shows which are already mounted.


0

If there are still people encountering this problem, I still could not fix it. I did find a working workaround. The following ruby script did the trick. It creates a folder called "keepalive" over and over. Just keep running this until infinity. $i =1 $num =0 begin puts("Inside the loop i = #$i" ) $i +=1 puts 'creating obj' system 'mkdir ...


0

Issuing grep -v root /proc/mounts > /etc/mtab; echo "/dev/sda9 / ext4 defaults 1 1" >> /etc/mtab fixed this problem. The startup issue was due to the mtab file having entries not properly removed during shutdown. Once the root filesystem was added to the mtab file (after boot), the shutdown occured properly and then startup also works fine. The ...


1

If nfs mount does not resides in fstab, means it is a temporary mount (lost after reboot). You can use df -h to check the mount point, if the first column is a hostname/ip, then it must be an nfs mount. # df -h ... 192.168.1.2:/ora_share 300G 206G 88G 71% /ora


0

Thanks for that. I use this in my scripts to unmount the entire chroot-tree: (Make sure to set $MNT accordingly) for dir in $(grep "$MNT" /proc/mounts | cut -f2 -d" " | sort -r) do umount $dir 2> /dev/null (( $? )) && umount -n $dir done


0

There is tool called mountpoint avaiable on many linux installations. The exitcode is 0 if the first argument is a mountpoint.


0

Although I don't think it's causing the problem here, your fstab entry is not 100% complete - you're missing the defaults in the mount options field. It should read: tmpfs /dev/shm tmpfs defaults,size=3g 0 0 That said, you will also need to change an init script for the fstab entry to take effect. See this bug report for more ...


0

A live cd rom is not writable when running a operating system from it. I really don't think you could implement any sort of persistence to it. A USB drive however can be used to install a operating system on, that would then allow you to obtain the persistence you require


0

Just install the Live CD on a USB stick, as you would do on a normal hard drive. This worked for me a few years ago. I booted my Live ISO in a VirtualBox, mounted the USB and installed it like any Ubuntu (Debian) derived distro. I hope my answer is not to short :)


1

On a linux system you can use findmnt: set '' for r in /* do findmnt "$r" || ! set '' "$r$@" && ls "$r" done That command will do the ls for the other mounts, and all of the / root-mount filenames are available in $@ when you're ready. So to list those you'd do: ls "$@"


0

For question a: { stat --printf='%d\n' / find / -mount -maxdepth 1 -type d -printf '%D/%p\n' } | awk -F/ 'NR==1{root=$1}; $1!=root{print "/"$2}' stat spits out the decimal device number of the root device. Then the find command lists the directories directly under /, together with the decimal device number. The output of both these commands is sent to ...


0

I accidentally discovered that changing the label "multisystem" using GParted to the name of the mount point "MULTISYSTEM" may help to resolve the issue that "match point does not match the label". For e.g. if you have created the folder "MULTISYSTEM" using the command : "~$ sudo mkdir /media/your_username/MULTISYSTEM" As my USB driver has Device ...


1

Try file -sL /dev/sdXY. Will give you some limited information without mounting the filesystem. $ file -sL /dev/sdc1 /dev/sdc1: Linux rev 1.0 ext2 filesystem data (mounted or unclean), UUID=aa84c5a8-6418-4952-b577-578f2a67af86, volume name "music" $


2

The tool looking inside an unmounted partition would need to interprete the filesystem's sturctures itself. Such tools exist for various filesystem (cpmtools, mtools, ...) and some filesystems have similar functionality primarily intended to be a debugging help (as example see debugfs). But why do you think, looking into the filesystem first is neccessary? ...


0

I am pretty sure, you forgot to mount it. mount /dev/sda1 /mnt should do that for you. In case you want to mount the second partition, be sure you installed hfsprogs and run mount /dev/sda2 /mnt


2

Thanks to the comment by @mikeserv I've found out how to revive it. I have only tested this on Linux 4.0.7, so for much earlier or much later versions it may not work. mount /dev/pts -o remount,gid=5,mode=620 Mounting a devpts filesystem in a chroot without using the newinstance option caused it to mount the same "instance" of /dev/pts, containing the ...


0

Point three and four don't make sense: /dev/sdb1 /media/usb1 vfat defaults 0 0 is ok, but is mounted with mount /dev/sdb1 or /media/usb1 /dev/sdb1 /media/usb1 msdos auto does not make sense, because "msdos" and "auto" are both for the filesystem type. You could try /dev/sdb1 /media/usb1 auto defaults 0 0 here. "noauto" in the options (here the "defaults" ...


1

Ensure you've recursively set the permissions to 777 after you've done the mount. Doing it before will have no effect. Also, please post the error you're getting. You might want to reconsider your choice of ext4 if you're using it as a removable drive. Frustratingly, there's still no option to ignore ownership and permissions on an ext4 filesystem. It's ...


0

NTFS and exFAT are both slow in Linux; one reason is that those filesystems are supported through the fuse layer only, which introduces considerable overhead, so it can't help being slower than a filesystem that is actually part of the kernel. Another reason is the filesystem itself. It's difficult to implement proprietary filesystems correctly and ...



Top 50 recent answers are included