Hot answers tagged fstab
15
If you want to reserve memory for cache and buffer:
echo 10 > /proc/sys/vm/vfs_cache_pressure
# 100 is the default value.
# Then you can limit the maximum amount of ram used by each app:
echo 8192 > /proc/sys/vm/max_map_count.
I also recommend a swapiness=30 and high /proc/sys/vm/dirty_writeback_centisecs and /proc/sys/vm/dirty_expire_centisecs ...
9
Firstly, I DO NOT recommend you continue using NTFS, as ntfs implemention in Linux would be performance and security trouble at any time.
There are several things you can do:
use some newer fs such as ext4 or btrfs
try to change your io scheduler, for example bfq
turn off swap
use some automatic preloader like preload
use something like systemd to preload ...
6
The Arch Linux Wiki has a comprehensive list of the field definitions in your /etc/fstab file, including those that you are asking about:
nodev - Don't interpret block special devices on the filesystem.
nosuid - Block the operation of suid, and sgid bits.
0 2 are, respectively, dump & pass:
<dump> - used by the dump utility to decide when to ...
6
It has to do with boot order. Highest priority is required for booting (/ and in my opinion /usr /var /tmp ...). The /boot filesystem can do with lower priority because by the time the system can start fsck's, it read the necessary files from boot already.
Filesystems for home directories etc. are lower priority during boot process.
6
The UUIDs don't change when you reorder the drives. However, your
sdc? entries might change. It's best practice not to rely on the
sd? numbering. Better use UUIDs or LABELs to address your
partitions.
Find the UUID or LABEL
as root:
blkid -o list -c /dev/null
Change the entries
Change the entries that use the /dev/sd? syntax (in your case /dev/sdc1) to ...
6
Generally not, but with newer versions of mount/swapon/fsck... on Linux (from util-linux 2.19) at least, you can have more files (with .fstab extension) in /etc/fstab.d. So you can have a /etc/fstab.d/00_header.fstab, /etc/fstab.d/50_middle.fstab, /etc/fstab.d/99_end.fstab.
Another approach if all you want is mount -a to run some command is have an entry ...
5
bind mirrors a filesystem (among other situatons, it's useful when setting a chroot inside which you need to have a "complete" system (like when unpacking/installing Gentoo).
Just simply like that, it mirrors a tree from A into B. I don't know for sure if it has any option, but I doubt it, it does not do more than, well, mirroring.
Unlike a symlink, which ...
5
Read ahead:
On 32 bit systems:
blockdev --setra 8388607 /dev/sda
On 64 bit systems:
blockdev --setra 4294967295 /dev/sda
Write behind cache:
echo 100 > /proc/sys/vm/dirty_ratio
This will use up to 100% of your free memory as write cache.
Or you can go all out and use tmpfs. This is only relevant if you have RAM enough. Put this in /etc/fstab. ...
4
pmount is generally to be used for mounting custom external devices that are not in fstab. What you experience is a feature of pmount - a part of its policy (see man pmount, search for fstab). If you want to permit normal users to mount cdrom, you can either comment it out in /etc/fstab and use pmount or set up the cdrom entry in fstab so that users are ...
4
Key-based authentication can only work if the ssh process can find your key. You presumably have your key in your home directory; but you've never told sshfs where to look for a key. At boot time, it would be root mounting all filesystems, therefore the key must be either in /root/.ssh or referenced in /root/.ssh/config.
I recommend mounting the filesystem ...
4
This is a side effect of how the debian initramfs operates. Initially the kernel creates a tmpfs for the root, and unpacks the initramfs, which is a compressed cpio archive, there. The programs and scripts in the initramfs mount the real root device and then chroot there. Simply ignore the first entry that lists the filesystem as rootfs, as that is just ...
4
It's safe to unmount one of the bind-mounted copies. After you run mount --bind /foo /bar, the kernel doesn't keep track of which of /foo or /bar came first, they're two mount points for the same filesystem (or part of a filesystem).
Note that if /foo is a mount point but /foo/wibble isn't, mount --bind /foo/wibble /bar makes /bar point to a part of the ...
4
As man mount describes it:
norecovery/noload
Don't load the journal on mounting. Note that if the filesystem was not unmounted cleanly, skipping the journal replay will lead to the filesystem containing inconsistencies that can lead to any number of problems.
You should really be only using this option to mount a filesystem so that you can attempt a ...
4
You can use \x20 for space.
That is hex value for ASCII (and utf-8 encoded) space.
Or you can use the octal variant \040.
So that would be (in fstab):
UUID=01CD72098BB21B70 /media/tusharmakkar08/Local\x20Disk1
# or
UUID=01CD72098BB21B70 /media/tusharmakkar08/Local\040Disk1
If you are not to familiar with ASCII fun install ascii and:
ascii # ...
3
You want that partition with a different file system to be mounted in Linux. So there can be two cases:
1. If the partition is to be mounted in every boot:
You have to create an empty directory where you want to mount that file-system. Suppose I want to mount a windows partition(/dev/sda1) to /myname, then i have to create an empty directory /myname
$ ...
3
Improving disk cache performance in general is more than just increasing the file system cache size unless your whole system fits the in RAM in which case you should use RAM drive (tmpfs is good because it allows falling back to disk if you need the RAM in some case) for runtime storage (and perhaps an initrd script to copy system from storage to RAM drive ...
3
So, question: can I force to map the drives with fixed path? I tried
using Labels but it didn't seem to work.
Use UUID:
$ ls -lF /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Sep 15 15:35 61965e0c-8aba-4207-9424-1350aa6e051e -> ../../sda2
lrwxrwxrwx 1 root root 10 Sep 15 15:35 e002a7bc-02da-47a8-ab98-1225e6ace6d5 -> ../../sda1
lrwxrwxrwx ...
3
The format of the fstab file is documented in the fstab(5) man page. The fifth column indicates whether the filesystem should be dumped; unless you know what this means, put 0. The sixth column indicates whether to check the filesystem at boot time; specify 1 for the root partition, 2 for all other internal filesystems, and 0 for external drives and ...
3
You could try an alternate approach, which is to recognize your device at the udev level and use /dev/mybook-partition in /etc/fstab. Put something like the following in /etc/udev/rules.d/dwilliams.rules:
KERNEL=="sd*", PROGRAM=="/sbin/blkid %N", RESULT=="C252-9CA3", SYMLINK+="mybook-partition"
The section on Auto mounting USB devices in the Arch wiki for ...
3
The line in /etc/fstab I eventually used was:
//10.1.0.15/G4\040320H /media/G4 cifs username=master,user 0 0
What solved the issue of not being prompted for the password as well as credentials= not working was installing mount.cifs via:
sudo apt-get install cifs-utils
Just like Michael Mrozek I assumed I had mount.cifs installed or else I ...
3
The UUID fb... is a partition. From the Information above, it is not
possible to tell if it is /dev/sda or anything else.
proc,sysfs,devpts are virtual file systems
tmpfs is some ramdisk-like filesystem
/usr/tmpDSK seems to be a file which is used as image to mount /tmp
3
Wikipedia isn't as good a reference as the man page. Both the the traditional ntfs driver and the now-preferred ntfs-3g support the umask option.
You shouldn't set umask to exclude executable permissions on directories, though, since you can't access files inside a non-executable directory. Instead, use separate values for fmask=0111 (non-directories) and ...
3
What are your mount options?
You should experiment with "hard,intr", or "soft" (with "timeo"), and possibly "retrans" depending on your client options. Using TCP instead of UDP may also help. The default is usually "hard".
Using "soft" is usually advised against, it can result in written data being lost. It's safe to use as read-only.
On latter linux ...
3
Do you mean you want to remove the noexec restriction on a directory in /home without removing it on the entire partition? If so, bind mounting the directory and remounting it with default options might work. But please conduct your own tests. Below is a dirty hack that seemed to work using EXT4, but it'd probably be cleaner/safer/better if you could bind ...
3
It seems that (whyever) in the first situation the volume is not mounted. You see the mount point i.e. the folder in the underlying file system. IMHO normal mount point folders should always belong to root:root and have 000 access rights as it does not make any sense to use them in a typical situation.
Mounting the volume replaces the mount point folder by ...
2
The filesystem is the Windows shared path, and the type is CIFS:
//file-server/ShareName /mnt/file-server-share cifs options 0 0
options can be all the usual mount options. You probably need to provide some sort of credentials; you can provide user and password options, or use credentials=/path/to/credentials/file and store username=... and password=... ...
2
Assuming this is Linux, you could also use tmpfs (see here for differences, i.e., why it might be advisable to use tmpfs), which is explained here and (see link) supports the options mode, gid and uid. There's the following paragraph in tmpfs.txt which might also be relevant:
These options do not have any effect on remount. You can change these
parameters ...
2
You can make a separate file with the following lines, and make it readable by root only:
username=<my username>
password=<my password>
Then in /etc/fstab, replace the username and password options with:
credentials=/path/to/your/file
2
No, mount does not "detect" any directories under a filesystem. It is not its purpose.
If you put /var, /opt and /usr all on a one partition, which is not the root partition of your system, you'll need to do two things:
Mount the partition under some separate, special directory - let's say /mnt/sysdirs
Bind-mount the directories at their proper places in ...
2
The field exists so you can define the order in which filesystems are checked. Different partitions on the same drive should not be checked at the same time since the IO going to each filesystem will compete with one another, and slow the whole process down. Filesystems on different physical disks could be set to check in the same pass to speed up the ...
Only top voted, non community-wiki answers of a minimum length are eligible
