EveryDayLinuxUser: This article explains why this particular user stopped using Ubuntu in favour of Scientific Linux.
Source: FULL ARTICLE at Linux Today
Tag Archives: Scientific Linux
Can't chgrp. Error – chgrp: changing group of `<file>': Invalid argument
By venmx
I found that I cannot chgrp for some reason with error:
chgrp: changing group of `’: Invalid argument
This happens on all NFS mounted disks on client machines.
We use AD (not my call) for authentication and it also provides groups.
We have a NFS server running Scientific Linux 6.3 which mounts SAN devices on FC connect. These are then exported via NFS. Clients are all CentOS 6.4.
The clients hard mounts the user’s home disk with intr,sync and various tuning options. The other disks use autofs.
AD is configured so that each user has a matching UID and GID, essentially making them the exclusive member of their own group. Not useful for sharing files unless you don’t mind making all your files accessibly by world, o+.
We need groups so that we can add members who are then able to chgrp what ever files they’d like to share with members of the same group. All seems pretty straight forward so far.
I used to run OpenLDAP with Kerberos to do all this, I had LDAP manage autofs and groups. Everything worked perfectly.
But now I cannot chgrp.
The permissions of the exported directories on the NFS server are:
drwx–x–x root root /san/home
drwxrwxrwx root root /san/otherdisks
But under home each user directory is owned by the user:
drwx–x–x user1 user1 /san/home/user1
NOTE: “other” means machines within same organization using same AD but built by other departments, “this” means the machines I built.
In the following scenarios it fails:
1. As AD user on “this” client machine on own home on “this” NFS server.
2. As AD user on “this” client machine on automounted disk on “this” NFS server.
3. As root on “this” client machine on automounted disk on “this” NFS server.
In the following scenarios it works:
1. As AD user on “this” client on local partitions where permissions allow.
2. As AD user logged in directly on “this” NFS server on any partition where permissions allow, including on SAN disks.
3. As root on “this” file server on any partition.
4. As AD user on “other” clients on export from “this” NFS server.
5. As AD user on “other” clients on export from “other” NFS server.
6. As AD user on “this” client on export from “other” NFS server.
This issue shows itself when I extract TAR files whilst on client machines to NFS exported shares as AD user or root, can’t chgrp!
I can do everything else, I can create, delete, even do newgrp and change my default group then create new files belonging to me with GID of new group. But still can’t chgrp
From: http://www.unix.com/red-hat/221091-cant-chgrp-error-chgrp-changing-group-file-invalid-argument.html
Open Recall: Bodhi Linux, Scientific Linux and Mageia Beta
The H Open: In this edition: catching up with the releases that happened over the long Easter weekend, including Mageia 3 beta 4, Scientific Linux 6.4 and Bodhi Linux 2.3.0.
Installing Nginx With PHP5 (And PHP-FPM) And MySQL Support On Scientific Linux 6.3
HowtoForge: This tutorial shows how you can install Nginx on a Scientific Linux 6.3 server with PHP5 support (through PHP-FPM) and MySQL support.
Using mod_spdy With Apache2 On Scientific Linux 6.3
HowtoForge: This tutorial explains how to use mod_spdy with Apache2 on Scientific Linux 6.3.
Scientific Linux 6.3 Samba Standalone Server With tdbsam Backend
HowtoForge: This tutorial explains the installation of a Samba fileserver on Scientific Linux 6.3 and how to configure it to share files over the SMB protocol as well as how to add users.
Installing And Using OpenVZ On Scientific Linux 6.3
HowtoForge: In this HowTo I will describe how to prepare a Scientific Linux 6.3 server for OpenVZ.
Expanding a volume group with system-config-lvm
By mmulqu
Good morning,
I’m working in a lab that generates a good amount of data and we’ve just about filled our 9.1TB RAID.
The system is a Dell PowerEdge 2950 running Scientific Linux 5.4 with a PERC H800 and a Dell PowerVault MD1200. The MD1200 has 12 bays, 6 of which were filled with 2TB drives that made up the original 9.1TB RAID5.
Recently, I purchased 6 new 2TB disks and added them to the 6 empty bays in the MD1200. Then, using Dell OpenManage, I reconfigured the virtual disk, adding the 6 new disks and converting to RAID6. That process took about two weeks and I ended up with about a 18.2TB virtual disk.
Now, the problem I’m having is expanding the volume group, which is still 9.1TB. I’m using the system-config-lvm package. The physical partition with all of my data is /dev/sdb1 and the volume group is called vg-home.
When I select ‘vg-home Physical view’ it shows me the volume group and a button below it that says ‘Extend Volume Group‘. I click on that button and a new window (title ‘Extend Volume Group‘) pops up. In this window, one of my choices is /dev/sdb 9312.50GB Uninitialized Disk Entity. The only other choices are my non-LVM /boot and / partitions, /dev/sda1 and /dev/sda3. My understanding is that the uninitialized disk entity on /dev/sdb is all of the newly added, non-LVM disk space.
However, once I click OK, I get a warning that states “All data on disk entity /dev/sdb will be lost! Are you certain that you wish to initialize it?”. Unfortunately, I don’t have a test system so I want to be absolutely sure I’m doing this correctly. Is this uninitialized disk entity the new space? Does the warning mean that I’ll lose the data on the LVM partition /dev/sdb1 as well or is it just saying that, if there is any data in the uninitialized space, it will be erased?
Thank you,
Matt