SL 5.4 - XFS project quota - XFS_QUOTAON: Invalid argument
Hi all, I have posted this a few weeks ago on the XFS mailing list, but did not receive an answer. So I'm trying here. We have an XFS filesystem on SL 5.4 with pquota accounting and enforcement. It was working well, but recently I had to disable enforcement for a short time. Now I want to switch it back on, but I get the error XFS_QUOTAON: Invalid argument. Does anyone know, what to do? Any suggestions are welcome. Thanks in advance. [r...@coffein raid]# xfs_quota -x -c state -a /raid User quota state on /raid (/dev/sdb1) Accounting: OFF Enforcement: OFF Inode: #18446744073709551615 (0 blocks, 0 extents) Group quota state on /raid (/dev/sdb1) Accounting: OFF Enforcement: OFF Inode: #259 (24 blocks, 3 extents) Project quota state on /raid (/dev/sdb1) Accounting: ON Enforcement: OFF Inode: #259 (24 blocks, 3 extents) Blocks grace time: [7 days 00:00:30] Inodes grace time: [7 days 00:00:30] Realtime Blocks grace time: [7 days 00:00:30] [r...@coffein raid]# xfs_quota -x -c enable -p -v /raid XFS_QUOTAON: Invalid argument Best Regards, Jan
udev rule to name USB disks after their serial number
We have a process here were users must push files onto USB disks. The
user logs in remotely to a machine which may have many USB disks
attached and he/she knows the serial number of the disk to write to.
In trying to do away with some complex, hacky scripts I'm trying to
udev-ise this. Ie. when a USB disk is plugged into the machine a symlink
to it is made that is /dev/disknumber-123456 where '123456' is the
serial number of the disk.
My udev rule is:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%E{serial}
It can create devices with symlink '/dev/disknumber-' but the
substitution of the ATRR{serial} bit seems to be impossible to get working.
The man page is usual includes no examples which might actually give me
the context I need to properly understand the 'printf-like substitution'
syntax that the developers are talking about.
Tim Edwards
Re: udev rule to name USB disks after their serial number
Tim Edwards wrote:
We have a process here were users must push files onto USB disks. The
user logs in remotely to a machine which may have many USB disks
attached and he/she knows the serial number of the disk to write to.
In trying to do away with some complex, hacky scripts I'm trying to
udev-ise this. Ie. when a USB disk is plugged into the machine a symlink
to it is made that is /dev/disknumber-123456 where '123456' is the
serial number of the disk.
My udev rule is:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%E{serial}
It can create devices with symlink '/dev/disknumber-' but the
substitution of the ATRR{serial} bit seems to be impossible to get working.
The man page is usual includes no examples which might actually give me
the context I need to properly understand the 'printf-like substitution'
syntax that the developers are talking about.
Tim Edwards
Tim,
I think you are confusing sysfs with environment variables. the %E{key}
is used for environment variables. The serial number is a SYSFS
attribute. Try changing %E{serial} to %s{serial} and see if it works.
Cheers,
Mark
--
Mr. Mark V. Stodola
Digital Systems Engineer
National Electrostatics Corp.
P.O. Box 620310
Middleton, WI 53562-0310 USA
Phone: (608) 831-7600
Fax: (608) 831-9591
Re: 'supervising' in process list
Think you're refering to: http://supervisord.org/ http://linux.die.net/man/3/supervisor HTH, Arnau On Thu, Mar 4, 2010 at 1:54 PM, Tim Edwards tedwa...@eso.org wrote: I've asked the syslog-ng mailing list but got no response here. I'm not sure if this is something related to syslog or a general thing but can someone explain to me what the 'supervising syslog-ng' process is doing, and where (what package or sub-system) it comes from? root 18622 1 0 08:53 ?00:00:00 supervising syslog-ng root 18623 18622 0 08:53 ?00:00:00 /opt/syslog-ng/sbin/syslog-ng --no-caps Thanks Tim Edwards
Re: udev rule to name USB disks after their serial number
On 05/03/10 15:16, Mark Stodola wrote:
Tim,
I think you are confusing sysfs with environment variables. the %E{key}
is used for environment variables. The serial number is a SYSFS
attribute. Try changing %E{serial} to %s{serial} and see if it works.
Cheers,
Mark
That didn't work unfortunately, my rules file now looks like this:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%s{serial}
Any other ideas?
Tim
Re: 'supervising' in process list
On 05/03/10 15:20, Arnau Bria wrote: Think you're refering to: http://supervisord.org/ http://linux.die.net/man/3/supervisor HTH, Arnau On Thu, Mar 4, 2010 at 1:54 PM, Tim Edwards tedwa...@eso.org mailto:tedwa...@eso.org wrote: I've asked the syslog-ng mailing list but got no response here. I'm not sure if this is something related to syslog or a general thing but can someone explain to me what the 'supervising syslog-ng' process is doing, and where (what package or sub-system) it comes from? root 18622 1 0 08:53 ?00:00:00 supervising syslog-ng root 18623 18622 0 08:53 ?00:00:00 /opt/syslog-ng/sbin/syslog-ng --no-caps Thanks Tim Edwards Maybe, however I can't see any of the config files or binaries mentioned in the documentation on their website on the system. Ie. a simple 'find / | grep -i supervis' returns nothing. Tim Edwards
Re: udev rule to name USB disks after their serial number
Tim Edwards wrote:
On 05/03/10 15:16, Mark Stodola wrote:
Tim,
I think you are confusing sysfs with environment variables. the %E{key}
is used for environment variables. The serial number is a SYSFS
attribute. Try changing %E{serial} to %s{serial} and see if it works.
Cheers,
Mark
That didn't work unfortunately, my rules file now looks like this:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%s{serial}
Any other ideas?
Tim
It works here, I just made a /etc/udev/rules.d/10-test.rules file with
your above line.
Next I ran 'udevcontrol reload_rules'. I then connected my Kingston USB
drive and /dev/disknumber-5B7A121E appeared.
Do you have any other custom rules that are mangling this one?
Cheers,
Mark
--
Mr. Mark V. Stodola
Digital Systems Engineer
National Electrostatics Corp.
P.O. Box 620310
Middleton, WI 53562-0310 USA
Phone: (608) 831-7600
Fax: (608) 831-9591
Re: udev rule to name USB disks after their serial number
On 05/03/10 15:36, Mark Stodola wrote:
Tim Edwards wrote:
On 05/03/10 15:16, Mark Stodola wrote:
Tim,
I think you are confusing sysfs with environment variables. the %E{key}
is used for environment variables. The serial number is a SYSFS
attribute. Try changing %E{serial} to %s{serial} and see if it works.
Cheers,
Mark
That didn't work unfortunately, my rules file now looks like this:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%s{serial}
Any other ideas?
Tim
It works here, I just made a /etc/udev/rules.d/10-test.rules file with
your above line.
Next I ran 'udevcontrol reload_rules'. I then connected my Kingston USB
drive and /dev/disknumber-5B7A121E appeared.
Do you have any other custom rules that are mangling this one?
Cheers,
Mark
It might just be a peculiarity of the USB stick I'm using to test it
then since it's creating a device '/dev/disknumber-' looking like it
can't find the serial number.
I'll try with one of the actual USB hard drives they're using when I
can get access to one next week.
Tim
Re: udev rule to name USB disks after their serial number
Tim Edwards wrote:
On 05/03/10 15:36, Mark Stodola wrote:
Tim Edwards wrote:
On 05/03/10 15:16, Mark Stodola wrote:
Tim,
I think you are confusing sysfs with environment variables. the %E{key}
is used for environment variables. The serial number is a SYSFS
attribute. Try changing %E{serial} to %s{serial} and see if it works.
Cheers,
Mark
That didn't work unfortunately, my rules file now looks like this:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%s{serial}
Any other ideas?
Tim
It works here, I just made a /etc/udev/rules.d/10-test.rules file with
your above line.
Next I ran 'udevcontrol reload_rules'. I then connected my Kingston USB
drive and /dev/disknumber-5B7A121E appeared.
Do you have any other custom rules that are mangling this one?
Cheers,
Mark
It might just be a peculiarity of the USB stick I'm using to test it
then since it's creating a device '/dev/disknumber-' looking like it
can't find the serial number.
I'll try with one of the actual USB hard drives they're using when I
can get access to one next week.
Tim
You can verify that using 'systool'. Try the following command:
systool -b usb -p -v
Find your USB drive in the output, and there should be something like this:
Device = 1-2
Device path = /sys/devices/pci:00/:00:1a.7/usb1/1-2
bConfigurationValue = 1
bDeviceClass= 00
bDeviceProtocol = 00
bDeviceSubClass = 00
bMaxPacketSize0 = 64
bMaxPower = 200mA
bNumConfigurations = 1
bNumInterfaces = 1
bcdDevice = 0100
bmAttributes= 80
configuration =
devnum = 3
idProduct = 1d00
idVendor= 13fe
manufacturer= Kingston
maxchild= 0
product = DataTraveler 2.0
serial = 5B7A121E
speed = 480
uevent = store method only
version = 2.00
If no serial exists for the device, the serial = line will be absent.
Cheers,
Mark
--
Mr. Mark V. Stodola
Digital Systems Engineer
National Electrostatics Corp.
P.O. Box 620310
Middleton, WI 53562-0310 USA
Phone: (608) 831-7600
Fax: (608) 831-9591
SL5.4 and Asus eee S101 netbook
I've installed SL5.4 on an ASUS eee S101 netbook that my lab has purchased. Reviews say Fedora 10 and Ubuntu 9.10 work flawlessly (Ubuntu). http://www.newegg.com/Product/Product.aspx?Item=N82E16834220595 I usually use SL, so I've installed 5.4. lscpi indicates that the ethernet controler is Atheros (AR8121 ...) and wireless is atheros (AR928X). There are no atheros entries in the other card adaptor lists in the network configuration submenus. So, neither the ethernet card nor wireless adaptors are recognized? The README file from downloading atheros driver from madwifi shows latest download is 2/08. README says lspci should show it as unknown and a 0x168x vendor ID. lspci -v indicates both ethernet (8324) and wireless (1a3b:1067) are unknown devices. I'm guessing madwifi is not going to not work. Looks like I need special software. For lab usage, I don't need networking. It would be nice to update software etc. I'd install ubuntu if it gave me networking capability and which is not available via current RHEL5 SL distro. thoughts? Bill Lutter
Re: SL5.4 and Asus eee S101 netbook
William Lutter wrote: I've installed SL5.4 on an ASUS eee S101 netbook that my lab has purchased. Reviews say Fedora 10 and Ubuntu 9.10 work flawlessly (Ubuntu). http://www.newegg.com/Product/Product.aspx?Item=N82E16834220595 I usually use SL, so I've installed 5.4. lscpi indicates that the ethernet controler is Atheros (AR8121 ...) and wireless is atheros (AR928X). There are no atheros entries in the other card adaptor lists in the network configuration submenus. So, neither the ethernet card nor wireless adaptors are recognized? The README file from downloading atheros driver from madwifi shows latest download is 2/08. README says lspci should show it as unknown and a 0x168x vendor ID. lspci -v indicates both ethernet (8324) and wireless (1a3b:1067) are unknown devices. I'm guessing madwifi is not going to not work. Looks like I need special software. For lab usage, I don't need networking. It would be nice to update software etc. I'd install ubuntu if it gave me networking capability and which is not available via current RHEL5 SL distro. thoughts? Bill Lutter This may be of help for the wireless (ath9k). http://linuxwireless.org/en/users/Drivers/ath9k/RHEL5 My guess is some more googling could shed light on the wired interface as well. Cheers, Mark -- Mr. Mark V. Stodola Digital Systems Engineer National Electrostatics Corp. P.O. Box 620310 Middleton, WI 53562-0310 USA Phone: (608) 831-7600 Fax: (608) 831-9591
Re: SL5.4 and Asus eee S101 netbook
On 5 March 2010 17:21, William Lutter wjlut...@wisc.edu wrote: I've installed SL5.4 on an ASUS eee S101 netbook that my lab has purchased. Reviews say Fedora 10 and Ubuntu 9.10 work flawlessly (Ubuntu). http://www.newegg.com/Product/Product.aspx?Item=N82E16834220595 I usually use SL, so I've installed 5.4. lscpi indicates that the ethernet controler is Atheros (AR8121 ...) and wireless is atheros (AR928X). There are no atheros entries in the other card adaptor lists in the network configuration submenus. So, neither the ethernet card nor wireless adaptors are recognized? The README file from downloading atheros driver from madwifi shows latest download is 2/08. README says lspci should show it as unknown and a 0x168x vendor ID. lspci -v indicates both ethernet (8324) and wireless (1a3b:1067) are unknown devices. I'm guessing madwifi is not going to not work. Looks like I need special software. For lab usage, I don't need networking. It would be nice to update software etc. I'd install ubuntu if it gave me networking capability and which is not available via current RHEL5 SL distro. Hi Bill, Have you checked the ELRepo Project? [1] The FAQ [2] may give you some hints. Regards, Alan. [1] http://elrepo.org [2] http://elrepo.org/tiki/FAQ
Re: SL5.4 and Asus eee S101 netbook
William Lutter wrote: I've installed SL5.4 on an ASUS eee S101 netbook that my lab has purchased. Reviews say Fedora 10 and Ubuntu 9.10 work flawlessly (Ubuntu). http://www.newegg.com/Product/Product.aspx?Item=N82E16834220595 I usually use SL, so I've installed 5.4. lscpi indicates that the ethernet controler is Atheros (AR8121 ...) and wireless is atheros (AR928X). There are no atheros entries in the other card adaptor lists in the network configuration submenus. So, neither the ethernet card nor wireless adaptors are recognized? The README file from downloading atheros driver from madwifi shows latest download is 2/08. README says lspci should show it as unknown and a 0x168x vendor ID. lspci -v indicates both ethernet (8324) and wireless (1a3b:1067) are unknown devices. I'm guessing madwifi is not going to not work. Looks like I need special software. For lab usage, I don't need networking. It would be nice to update software etc. I'd install ubuntu if it gave me networking capability and which is not available via current RHEL5 SL distro. ath9k is included in 5.5's kernel. If you're feeling adventurous you can grab the sources for the beta and compile them yourself. Or you can wait a while for SL 5.5's release. http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.5.b1/html/Release_Notes/#id3488732 -- Garrett Holmstrom University of Minnesota School of Physics and Astronomy Systems Staff
Fwd: Re: SL5.4 and Asus eee S101 netbook
I've installed the suggested kernel kernel-2.6.18-189.el5.jwltest.105.i686.rpm. This may be of help for the wireless (ath9k). http://linuxwireless.org/en/users/Drivers/ath9k/RHEL5 No go. My supervisor prefers the netbook not have internet capability, so not an issue. I will provide this feedback. The wireless adaptor in network configuration now is identified as atheros AR928X. It is unknown still in lspci output. Starting the device via network configuration menus yields a siocsifflags unknown error 132. Or, sudo ifconfig wlan0 up SIOCSIFFLAGS: Unknown error 132 Ubuntu forums suggest rfkill. I surmise rfkill is an ubuntu hack that kills wifi drivers. Lots of web exchanges on this. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/464559 Thanks for the suggestions, Bill Lutter ---BeginMessage--- William Lutter wrote: I've installed SL5.4 on an ASUS eee S101 netbook that my lab has purchased. Reviews say Fedora 10 and Ubuntu 9.10 work flawlessly (Ubuntu). http://www.newegg.com/Product/Product.aspx?Item=N82E16834220595 I usually use SL, so I've installed 5.4. lscpi indicates that the ethernet controler is Atheros (AR8121 ...) and wireless is atheros (AR928X). There are no atheros entries in the other card adaptor lists in the network configuration submenus. So, neither the ethernet card nor wireless adaptors are recognized? The README file from downloading atheros driver from madwifi shows latest download is 2/08. README says lspci should show it as unknown and a 0x168x vendor ID. lspci -v indicates both ethernet (8324) and wireless (1a3b:1067) are unknown devices. I'm guessing madwifi is not going to not work. Looks like I need special software. For lab usage, I don't need networking. It would be nice to update software etc. I'd install ubuntu if it gave me networking capability and which is not available via current RHEL5 SL distro. thoughts? Bill Lutter This may be of help for the wireless (ath9k). http://linuxwireless.org/en/users/Drivers/ath9k/RHEL5 My guess is some more googling could shed light on the wired interface as well. Cheers, Mark -- Mr. Mark V. Stodola Digital Systems Engineer National Electrostatics Corp. P.O. Box 620310 Middleton, WI 53562-0310 USA Phone: (608) 831-7600 Fax: (608) 831-9591 ---End Message---
Re: SL5.4 and Asus eee S101 netbook
Garrett Holmstrom wrote: ath9k is included in 5.5's kernel. If you're feeling adventurous you can grab the sources for the beta and compile them yourself. Or you can wait a while for SL 5.5's release. http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.5.b1/html/Release_Notes/#id3488732 You don't need to compile them yourself, Red Hat testing kernel binaries are available here: http://people.redhat.com/jwilson/el5/ Kernel -186.el5 shipped as part of RHEL5.5b1. Alternatively, as Alan Bartlett stated, grab the drivers from ELRepo. Hope that helps.
