General :: Know If Noatime Or Relatime Is Default Mount Option In Kernel?
Aug 1, 2011
I was trying to know if relatime or noatime was set on a filesystem, but i didn't found the information, neither in /etc/fstab, neither in kernel boot options.
First of all, it seems clear that i don't have the "normal" behaviour on atime:
If the filesystem is mounted with noatime option does it influence find -atime behaviour? I tested and it looks that find is able to see access time but why should it if mounted with noatime? Or maybe it depends on the type of filesystem (I`m using XFS)?EDIT: Looks the answer is [URL]htmlIf a file system has been mounted with this option, reading accesses to the file system will no longer result in an update to the atime information associated with the file like we have explained above. The importance of the noatime setting is that it eliminates the need by the system to make writes to the file system for files which are simply being read. Since writes can be somewhat expensive, this can result in measurable performance gains. Note that the write time information to a file will continue to be updated anytime the file is written to.
I have an SSD and I'm trying to set noatime to save writes. I didn't do this at the time of install, so I edited /etc/fstab later on. I noticed, however, that when I right-click on a file and view its properties, it still gives me a "modified" and "accessed" time. Did I do something wrong? Here is my fstab:
I have had Linux running in our product that has several serial ports.(Another Ethernet to Serial port translator). It has been running OK for about 6 years, using kernel 2.6.11, then 2.6.18. Now I just got 2.6.39.1 running and suddenly I get these "I/O Possible" messages and my programs shutdown. I found elsewhere that the cure for this is to put a "signal(SIGIO, SIG_IGN)" call to stop this signal from crashing the program. This works, but I would really like to know the reason that this started happening in the first place.
Could there possibly be a 'config' option I missed that causes this? It just surprises me that the kernel writers would implement something that has such a large impact on the existing code base, causing anyone using serial ports, or anything else that might trigger a SIGIO, to have to edit, recompile, and redistribute their programs.
How to change the kernel behavior, short of going in and hacking the kernel. Or at least an idea as to why they would have changed the default behavior.
I have Suse 10 and Suse 11 and I need to add the option elevator=noop
Code: Suse 11
Code:
By the way I think I added correctly
Ok my question is: I can add this noop option on the fly by
Code:
But since I have sdb and sdc... I have to run that command three times it does not bother me I am worry about is what happens when my server is rebooted.
There won't be any noop option for sdb and sdc since they are not included on my boot parameter.
How can I automatically add noop to my sdb and sdc?
As from Hardy 8.04, Ubuntu started to use relatime as default. I just noticed today that the entries in Lucid's default /etc/fstab do not have relatime. Surely this is an important omission? On slow computers, it will decrease performance, and on any computer, it decreases the life of the hard drive. That's what I had understood. Or is there something about ext4 that makes this different?
I have a loadable module, simple enough I believe it should run on any 2.6 kernel. I want to force the load and test that assumption. How can I do it?
ismod does not seem to notice the -f in 2.7 modprobe has -f but cannot locate the module.No go. So I read the manpage for modprobe which says: modprobe looks in the module directory /lib/modules/'uname -r'.So I copied MYMODULE.ko to /lib/modules/2.6.(the only directory in here) and type: modprobe -f MYMODULE.ko.Still can't locate MYMODULE.ko.I notice there are no other .ko modules in that directory; so I go in deeper to kernel/drivers/char, guessing about the char directory, and copy MYMODULE.ko there.
I downloaded centos from their official bittorrent.It contained two iso files and md5sum.txt,sha1sum.txt and sha256sum.txt and also md5sum.txt.asc,sha1sum.txt.asc and sha256sum.txt.asc.Now when I mount iso file to virtual drive there is no autoplay option.Can you tell me how to install it.I dont see any setup file?
When using make menuconfig - under Device Drivers --> Character Devices --> there should be an option with the label "Enhanced Real Time Clock Support" (CONFIG_JS_RTC).
The problem is that this option seems to only show up while using the menu method when other options are either enabled or disabled and I've entirely forgotten what should be what. I swear fingered it out once.
This is on an older computer (P4) so HPET is no good.
You would think that disabling the HPET option would enable the RTC option but that does not appear to be the case.
I understand I can just add the option to the .config file and avoid this hassle but I'm very interested to know how to make this work.
To show my appreciation I will do something nice for you such as call you a nice name or tell you that you are pretty (or ugly if that's what you prefer).
Is the mount point for external media (like USB) always /media?
Because in a Debian system, if I plug in any USB device that goes to the /media folder. So is it the case with all the other Linux flavors like Fedora, Ubuntu, etc. If a USB device is automatically mounted will it always go to the /media directory?
I am not concerned about the name of the devices. I am looking for every external media (like USB) to be listed under /media directory so that my code can run on any flavor of Linux.
I've accidentaly corrupted my fstab and cut the ends of lines. There are now disk uid, mount point, filesystem for root and swap, but the mount parameters are missing.The system boots as readonly. What are default fstab mount parameters in Debian for ext4 root and swap?
I have a shared, family computer which has USB drives attached to it. Multiple users can be logged in, that sort of thing. All of the users have been added to "Access external storage devices automatically", however I've noticed that when one user plugs in a USB device, the other users can't see it without unmounting/remounting. When a drive is mounted, it seems to mounted at:
What I want to do is change the default mount group settings, to:
drwxrwx--- 5 jdoe family 4096 2011-08-10 12:03 DriveName/
I know I can do this through fstab, but as far as I know that forces you to name the drive/mount point and that's not what I'm looking for, what if a user adds a NEW usb device and wants it shared with the other users?
I dual-boot my machine and I want it to default to boot into windows so that whenever I restart the machine remotely from my home it will be able to get back into Windows (instead of Ubuntu).
The problem is that every time Ubuntu upgrades the kernel, I have to reset the default boot item of grub back to windows. This is because the grub menu loader uses positions i.e. 6 for default OS to boot. And when Ubuntu installs a new kernel it changes that order.
I am looking for a way to configure grub to remember its default boot item under kernel updates.
Possible Duplicate:Make grub keep its default boot under kernel updates.I have just installed Linux with my windows 7 pre-installed and i got it working fine. Since i use windows 7 more than linux, i would like to have "Windows 7" option on the top of "Linux" option.
"When i have turn on my computer, the first thing i see is an Option asking me whether i want to use windows 7 or Linux and there's a countdown timer below it which is 10seconds countdown and if i don't select it on time, it will automatically select the first choice which at the moment i've got Linux pre-set as my first choice."
I am trying to make a copy of the SD card that my TS-7800 SBC boots from. When I plug the SD into my opensuse pc I get this error. Error mounting: mount exited with exit code 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so There are four partitions on this card and I can only access one of them.
dmesg | tail gives me this
[894.422497] EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
when I do e2fsck -p /dev/sdb4 I get
e2fsck: Bad magic number in super-block while trying to open /dev/sdb4 /dev/sdb4: The superblock could not be read or does not describe a correct ext2 file system. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> I was hoping I could just plug in both cards and do this dd if=/dev/sdb of=/dev/sdc to copy everything and have a back up SD card.
differences between Kernel Default and Kernel Desktop? I've found some past threads like this link and this other link, and some other google info, which suggest the only difference would be the io scheduler. Also, I see the default grub choice is "Desktop" and not "Default", so I take this as a suggestion to prefer one over the other.
However, my broadcom 4312 wireless only works on the "default" and not on the "desktop" kernel, so I guess there must be other differences. I just want to evaluate which one is the less long-term risk option to go.
I have just tried to update my kernel from 2.6.24.5 to 2.6.39-rc3 on a Slackware 12.1 distribution. I have successfully updated the kernel before, but it was from a newer distribution and newer kernel(Slackware 13.1 and 2.6.33.4). After I updated and rebooted, I got the following error:
Code: List of all partitions: 0300 4194302 hda driver: ide-cdrom 0800 312571224 sda driver: sd 0801 244197560 sda1 00000000-0000-0000-0000-000000000sda1 0802 68372640 sda2 00000000-0000-0000-0000-000000000sda2 No filesystem could mount root, tried: romfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (8,1) Pid: 1, comm: swapper Not tainted 2.6.39-rc3-smp #1 .....
Did a fresh install of 64-bit Natty on day 1, and have an irksome issue when logging in. Once I'm logged in, Keyring prompts me to type the default keyring password. This happens every time I log in.
The problem is, the option to unlock the keyring automatically at login is dimmed, and only the other 3 options are selectable.
I opened the "Passwords and Encryption Keys" applet and saw 2 entries under "passwords", both named "Network secret for Auto [my network name]/802-11-wireless-security/psk". I see no option here to allow either of these to automatically unlock at login.
how I can get Ubuntu to log into my wireless network automatically instead of asking for the default keyring password each time after log in?
After searching the boards, I dug through the udev man pages and rule files looking for a way to modify the default automount options for USB flash drives. Apparently, the options are somewhere else. Is there a simple way to add noatime to the default mount options?
Currently, the flash drive is automounted as follows:
I'm using Fedora 12, beta RC 2 in case that makes a difference.
where I could lok to resolve this conflict?The command-line: lpotions -p printer -lReports the saved values with an "*" and (for evample: PageSize=Letter, InputSlot=MPT) seem to be in effect. However, the desired page size has been set and subsequently reports in both the web-based CUPS and the YaST printer utilities, as A4
I have openSuse 11.2 along with Windows, I get an option on boot to choose between the two OS, but the default is suse. How can I change the default load to Windows
I was wondering how I can make Windows XP the first and default option on my Grub 2. I use Ubuntu 9.10 through a semi-dedicated partition on my second hard drive, if that helps. I use Grub 2 just cause I have a grub.cfg file, and here it is.
Code: # # DO NOT EDIT THIS FILE # # It is automatically generated by /usr/sbin/grub-mkconfig using templates
