Error Reading Tunables From Nextboot
Ousterhout: "Re: ioo / vmo" Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Date: Mon, 31 Jan 2005 15:46:01 -0500 To: aix-l@Princeton.EDU This is not a p570, but ioo is -r-xr-x--- for me, both on aix 5.2 and on 5.3, and it correctly returns information. Mike Tibor
/ vmo" Next in thread: Mike Tibor: "Re: ioo / vmo" Reply: Mike Tibor: "Re: ioo / vmo" Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Date: Mon, 31 Jan 2005 14:58:10 -0600 To: aix-l@Princeton.EDU There are files in /etc/tunables that need to have the correct permissions also. This will determine what happens on your next reboot. Here's what I have in that directory. -rw-r--r-- 1 root system 65 Dec 13 09:11 lastboot.log -rw-r--r-- 1 root system 10964 Dec 13 09:11 lastboot http://unix.derkeiler.com/Mailing-Lists/AIX-L/2005-01/0293.html -rw-r--r-- 1 root system 2082 Dec 13 10:24 nextboot Sounds like someone may have gotten a little crazy with wildcarded permissions of 0000. I'd go through your other directories and see if anything else was affected. /etc and /usr are fairly important. Regards, Darryl -----Original Message----- From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of Mike Tibor Sent: Monday, January 31, 2005 http://unix.derkeiler.com/Mailing-Lists/AIX-L/2005-01/0294.html 2:34 PM To: aix-l@Princeton.EDU Subject: ioo / vmo I'm trying to get/set some parameters using ioo and vmo on my p570 running 5.3, and I'm running into some goofy file permissions problems. By default, it appears that a large number of files in /usr/bin and /usr/sbin have 0000 permissions. This includes ioo* and vmo*. I set ioo, ioo64, vmo and vmo64 to 0550, but now I'm getting the following: root@aixdb2-1:/usr/sbin# ioo -a ioo: 1485-121 Error reading tunables from nextboot file Are there other files ioo may be trying to call which are mode 0000? I've already found and chmod'd /usr/sbin/tun*, but that didn't help. Anybody know why these files are mode 0000 by default? Thanks, Mike Next message: Juan Camilo Yanquen: "Re: Define "logged in as ROOT"" Previous message: Ferenc Gyurcsan: "Re: ioo / vmo" Maybe in reply to: Mike Tibor: "ioo / vmo" Next in thread: Mike Tibor: "Re: ioo / vmo" Reply: Mike Tibor: "Re: ioo / vmo" Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Flag as inappropriate (AWS) Security UNIX Linux Coding Usenet Mailing-ListsNewsgroupsAboutPrivacyIm
[ -j ] [ -J journal-options ] [ -m reserved-blocks-percentage ] [ -o [^]mount-options[,...] ] [ -r reserved-blocks-count ] [ -s sparse-super-flag ] [ -u user ] [ -g group ] [ -C mount-count ] http://manpages.ubuntu.com/manpages/xenial/man8/tune2fs.8.html [ -E extended-options ] [ -L volume-name ] [ -M last-mounted-directory ] [ -O [^]feature[,...] ] [ -Q quota-options ] [ -T time-last-checked ] [ -U UUID ] device DESCRIPTION tune2fs allows the system administrator to adjust various tunable filesystem parameters on Linux ext2, ext3, or ext4 filesystems. The current values of these options can be displayed by using the -l option to tune2fs(8) program, or by using the dumpe2fs(8) program. error reading The device specifier can either be a filename (i.e., /dev/sda1), or a LABEL or UUID specifier: "LABEL=volume-name" or "UUID=uuid". (i.e., LABEL=home or UUID=e40486c6-84d5-4f2f-b99c-032281799c9d). OPTIONS -c max-mount-counts Adjust the number of mounts after which the filesystem will be checked by e2fsck(8). If max-mount-counts is 0 or -1, the number of times the filesystem is mounted will be disregarded by e2fsck(8) and the kernel. Staggering the mount-counts at which filesystems are forcibly error reading tunables checked will avoid all filesystems being checked at one time when using journaled filesystems. You should strongly consider the consequences of disabling mount-count-dependent checking entirely. Bad disk drives, cables, memory, and kernel bugs could all corrupt a filesystem without marking the filesystem dirty or in error. If you are using journaling on your filesystem, your filesystem will never be marked dirty, so it will not normally be checked. A filesystem error detected by the kernel will still force an fsck on the next reboot, but it may already be too late to prevent data loss at that point. See also the -i option for time-dependent checking. -C mount-count Set the number of times the filesystem has been mounted. If set to a greater value than the max-mount-counts parameter set by the -c option, e2fsck(8) will check the filesystem at the next reboot. -e error-behavior Change the behavior of the kernel code when errors are detected. In all cases, a filesystem error will cause e2fsck(8) to check the filesystem on the next boot. error-behavior can be one of the following: continue Continue normal execution. remount-ro Remount filesystem read-only. panic Cause a kernel panic. -E extended-options Set extended options for the filesystem. Extended options are comma separated, and may take an a