Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm unable to update python because there are files in /usr/lib/python3.3/test/*
I am unable to delete the files and I'm unable to chown them.
Code:
[root@corp test]# chown: changing ownership of '__pycache__/test_lib2to3.cpython
chown: changing ownership of '__pycache__/test_lib2to3.cpython-33.pyo': Operation not permitted
I had the lovely idea of mirroring two flash drive for this server (router). Not the best experience... I've had them crash and I've had to do 15 minutes of fsck to fix. Forgetting to move the log files played a part in that.
Anyways, how the heck can I delete these files? I'll end up restoring from backup tonight if no one comes up with any bright ideas.
BTW, the server is functional (on second thought, functional might be the wrong word). The only issue I see is that python won't install/update and I can't create my vlans with vconfig:
Code:
[root@corp test]# vconfig
-bash: /usr/bin/vconfig: No such file or directory
Behavior like this usually occurs when you install 32 bit software on a 64 bit system without multilib enabled. May this be the case here? You can check that with
For the two strange files, try changing the owner and group to "root" and then see if you can run your update. (From the owner and group values displayed, and the strange size, I'd suspect that the directory file was damaged.)
Behavior like this usually occurs when you install 32 bit software on a 64 bit system without multilib enabled. May this be the case here? You can check that with
Code:
file /usr/bin/vconfig
I never enabled multilib on that server. This doesn't make much sense to me:
For the two strange files, try changing the owner and group to "root" and then see if you can run your update. (From the owner and group values displayed, and the strange size, I'd suspect that the directory file was damaged.)
Code:
[root@corp test]# find /usr/lib/python3.3/ | xargs ls -lahtr
-r--r--r-- 1 262144 1140850688 20K Dec 22 15:11 /usr/lib/python3.3/test/decimaltestdata/dqDivideInt.decTest
-rwxr--r-- 1 196608 adm 257G Dec 22 15:11 /usr/lib/python3.3/test/__pycache__/test_lib2to3.cpython-33.pyo
-rw-r----- 1 16 71303170 48K Dec 22 15:11 /usr/lib/python3.3/test/__pycache__/test_poll.cpython-33.pyo
/usr/lib/python3.3/test/decimaltestdata/quantize.decTest:
total 8.0K
drw-r--r-- 2 8388608 65537 4.0K Dec 22 15:11 .
drwx------ 3 root root 4.0K May 21 20:05 ..
/usr/lib/python3.3/:
total 96K
drwxr-xr-x 3 root root 4.0K May 21 16:44 .
drwxr-xr-x 111 root root 68K May 23 11:00 ..
drwxr-xr-x 4 root root 20K May 23 19:36 test
/usr/lib/python3.3/test/decimaltestdata:
total 36K
-r--r--r-- 1 262144 1140850688 20K Dec 22 15:11 dqDivideInt.decTest
drw-r--r-- 2 8388608 65537 4.0K Dec 22 15:11 quantize.decTest
drwx------ 3 root root 4.0K May 21 20:05 .
drwxr-xr-x 4 root root 20K May 23 19:36 ..
/usr/lib/python3.3/test/__pycache__:
total 96K
-rwxr--r-- 1 196608 adm 257G Dec 22 15:11 test_lib2to3.cpython-33.pyo
-rw-r----- 1 16 71303170 48K Dec 22 15:11 test_poll.cpython-33.pyo
drwx------ 2 root root 40K May 21 20:33 .
drwxr-xr-x 4 root root 20K May 23 19:36 ..
/usr/lib/python3.3/test:
total 68K
drwxr-xr-x 3 root root 4.0K May 21 16:44 ..
drwx------ 3 root root 4.0K May 21 20:05 decimaltestdata
drwx------ 2 root root 40K May 21 20:33 __pycache__
drwxr-xr-x 4 root root 20K May 23 19:36 .
Code:
[root@corp decimaltestdata]# chown root dqDivideInt.decTest ; chgrp root dqDivideInt.decTest
chown: changing ownership of 'dqDivideInt.decTest': Operation not permitted
chgrp: changing group of 'dqDivideInt.decTest': Operation not permitted
Code:
[root@corp __pycache__]# chown root test_lib2to3.cpython-33.pyo ; chgrp root test_lib2to3.cpython-33.pyo
chown: changing ownership of 'test_lib2to3.cpython-33.pyo': Operation not permitted
chgrp: changing group of 'test_lib2to3.cpython-33.pyo': Operation not permitted
Then something got seriously wrong on that system, the file output clearly shows that you have a 32 bit executable of vconfig installed, but you stated that this is a 64 bit installation of Arch.
Ya, the system is probably screwed. However, this is on my workstation:
Code:
[root@workstation ~]# uname -a
Linux workstation 3.9.3-1-ARCH #1 SMP PREEMPT Sun May 19 22:50:29 CEST 2013 x86_64 GNU/Linux
[root@workstation ~]# file /usr/bin/vconfig
/usr/bin/vconfig: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, stripped
[root@workstation ~]# vconfig
Expecting argc to be 3-5, inclusive. Was: 1
Usage: add [interface-name] [vlan_id]
rem [vlan-name]
set_flag [interface-name] [flag-num] [0 | 1]
set_egress_map [vlan-name] [skb_priority] [vlan_qos]
set_ingress_map [vlan-name] [skb_priority] [vlan_qos]
set_name_type [name-type]
* The [interface-name] is the name of the ethernet card that hosts
the VLAN you are talking about.
* The vlan_id is the identifier (0-4095) of the VLAN you are operating on.
* skb_priority is the priority in the socket buffer (sk_buff).
* vlan_qos is the 3 bit priority in the VLAN header
* name-type: VLAN_PLUS_VID (vlan0005), VLAN_PLUS_VID_NO_PAD (vlan5),
DEV_PLUS_VID (eth0.0005), DEV_PLUS_VID_NO_PAD (eth0.5)
* bind-type: PER_DEVICE # Allows vlan 5 on eth0 and eth1 to be unique.
PER_KERNEL # Forces vlan 5 to be unique across all devices.
* FLAGS: 1 REORDER_HDR When this is set, the VLAN device will move the
ethernet header around to make it look exactly like a real
ethernet device. This may help programs such as DHCPd which
read the raw ethernet packet and make assumptions about the
location of bytes. If you don't need it, don't turn it on, because
there will be at least a small performance degradation. Default
is OFF.
I hope you checked extended attributes, right? Then it seems to be a good example of ext2 bad practices; the only possibility I can imagine is to hack inodes manually
I belive these are separate issues.
The vconfig doesn't make any sense. It works on some systems and not on others. I thought it was because the 8021q module wasn't loaded - but that didn't make any difference. FML
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.