Hey Group; What the heck (cleaned up ) is causing SuSE to tell me as root (not "su") that I don't have permission to install a program. I then do "l /usr/lib/directory" and get "Permission denied" "root" installed it and is trying to "l" it. I am about ready to dump SuSE if this kind of problem persist It is like a hidden set of permissions. -- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
On Sunday 17 July 2005 02:48, Donn Washburn wrote:
Hey Group;
What the heck (cleaned up ) is causing SuSE to tell me as root (not "su") that I don't have permission to install a program. I then do "l /usr/lib/directory" and get "Permission denied" "root" installed it and is trying to "l" it.
I am about ready to dump SuSE if this kind of problem persist
It is like a hidden set of permissions.
Classic signs of a corrupted file system. There are ways to deny root permissions on objects, but if you (the administrator) don't know about it, then I can almost guarantee it hasn't been done. Boot the rescue system and run reiserfsck on your partition (I'm guessing you're running reiser. So far every instance of file system corruption that I've seen that didn't involve a system crash has been in reiser)
Anders Johansson wrote:
On Sunday 17 July 2005 02:48, Donn Washburn wrote:
Hey Group;
What the heck (cleaned up ) is causing SuSE to tell me as root (not "su") that I don't have permission to install a program. I then do "l /usr/lib/directory" and get "Permission denied" "root" installed it and is trying to "l" it.
I am about ready to dump SuSE if this kind of problem persist
It is like a hidden set of permissions.
Classic signs of a corrupted file system. There are ways to deny root permissions on objects, but if you (the administrator) don't know about it, then I can almost guarantee it hasn't been done.
Boot the rescue system and run reiserfsck on your partition (I'm guessing you're running reiser. So far every instance of file system corruption that I've seen that didn't involve a system crash has been in reiser)
Thanks for the reply You may be correct - but it is my /usr/include directory it is on the same one as my "/" partition. It seems to be working correctly. -- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
Quoting Donn Washburn
Anders Johansson wrote: [snip]
Classic signs of a corrupted file system. There are ways to deny root permissions on objects, but if you (the administrator) don't know about it, then I can almost guarantee it hasn't been done.
Boot the rescue system and run reiserfsck on your partition (I'm guessing you're running reiser. So far every instance of file system corruption that I've seen that didn't involve a system crash has been in reiser)
Thanks for the reply
You may be correct - but it is my /usr/include directory it is on the same one as my "/" partition. It seems to be working correctly.
Donn, I agree with Anders, boot the rescue disk and run fsck on all partitions. ReiserFS has some desireable characteristics, but extreme robustness is not one of them. I am slowly migrating away from ReiserFS. Less performance and less efficient use of hard disk space I can live with, FS corruption I can't. I have seen similar symptoms in the past and uttered probably similar epithets about what do you mean root can't access this. I no longer use ReiserFS for any partition but /home. And it only because I keep /home across OS upgrades (by clean install). Someday soon when I am sure I have backups I can trust, I'll reformat the /home partition with some other FS, probably ext3 and restore the data. Jeffrey
Jeffrey L. Taylor wrote:
Quoting Donn Washburn
: Anders Johansson wrote:
[snip]
Classic signs of a corrupted file system. There are ways to deny root permissions on objects, but if you (the administrator) don't know about it, then I can almost guarantee it hasn't been done.
Boot the rescue system and run reiserfsck on your partition (I'm guessing you're running reiser. So far every instance of file system corruption that I've seen that didn't involve a system crash has been in reiser)
Thanks for the reply
You may be correct - but it is my /usr/include directory it is on the same one as my "/" partition. It seems to be working correctly.
Donn, I agree with Anders, boot the rescue disk and run fsck on all partitions. ReiserFS has some desireable characteristics, but extreme robustness is not one of them. I am slowly migrating away from ReiserFS. Less performance and less efficient use of hard disk space I can live with, FS corruption I can't. I have seen similar symptoms in the past and uttered probably similar epithets about what do you mean root can't access this.
I no longer use ReiserFS for any partition but /home. And it only because I keep /home across OS upgrades (by clean install). Someday soon when I am sure I have backups I can trust, I'll reformat the /home partition with some other FS, probably ext3 and restore the data.
Jeffrey
Well I have deal with UNIX for over 20 years and fsck.reiserfs can only safetlybe run on a unmounted file system. So, I figured that rebooting would solve that kind of problem. Good news it did! I have been running reiserfs since it came out and never had a major problem. I do agree that maybe ext3 might be better. I was installing upgraded GL libs. Jeffrey are you in Austin, TX or your ISP just liked the name -- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
Quoting Donn Washburn
Well I have deal with UNIX for over 20 years and fsck.reiserfs can only safetlybe run on a unmounted file system. So, I figured that rebooting would solve that kind of problem. Good news it did!
I have been dealing with UNIX since 1977 or '78, Linux for over 6 years.
I have been running reiserfs since it came out and never had a major problem. I do agree that maybe ext3 might be better. I was installing upgraded GL libs.
I have had several corrupted ReiserFS and will not be formatting any new partitions with it for a while at least. Now one of the corruptions was due to a failing hard disk, but for the rest, the cause is unknown. I work my systems hard. And power is very flakey out here in East Travis County. All three desktops are now on UPSes. Plus the VCR; missed too many programs because the power died and reset the clock. We are getting 1-3 power outages a day right now.
Jeffrey are you in Austin, TX or your ISP just liked the name
austinblues.dyndns.org is a dynamic IP address for my home system(s). I am in or at least near Austin, TX (Austin post office and electricity, but outside city limits). Austin Blues was a club on East 6th Street that was part of my reasons for moving here. It was closed by the time I actually moved here six years ago. The place has had two or three businesses in it since then. Tough business environment. Jeffrey
Donn Washburn wrote:
Jeffrey L. Taylor wrote:
Quoting Donn Washburn
: Anders Johansson wrote:
[snip]
<STUFF DELETED>
Well I have deal with UNIX for over 20 years and fsck.reiserfs can only safetlybe run on a unmounted file system. So, I figured that rebooting would solve that kind of problem. Good news it did!
I have been running reiserfs since it came out and never had a major problem. I do agree that maybe ext3 might be better. I was installing upgraded GL libs.
Jeffrey are you in Austin, TX or your ISP just liked the name
I'd still recommend running reiserfsck from rescue. I've had more than my fair share of filesystem corruptions, back in ext2 it was so severe that I'd changed everything (including the power supply) except the case and it turned out to be multiple bad hardware bits. With the many reiserfs problems, it's been CPU's, memory, hard drives, bad IDE controllers on motherboards and combinations of the above, but not one single instance that's proved to have been caused by reiserfs. If you follow the kernel mailing list, you'll see problems in ext3 also and bad hardware will always bite you whatever filesystem you use. On the basis of my troubles over the years, I don't see a reason to switch from reiserfs. I think what I need on boxes that run 2x7x365 1/4 is a stack of spare hard drives to be swapped at the first sign of trouble after recovering by running reiserfsck. Hard drive reliability is still very poor, even on big EMC raid subsystems, the most frequent activity is replacing SCSI hard drives, so much so that customers are often left a number of drives so they can replace failing ones themselves. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Sid Boyce wrote:
On the basis of my troubles over the years, I don't see a reason to switch from reiserfs.
If you (or someoneelse) feel like trying out another journaled filesystem, there's always JFS. I can't actually say if it's any better or not, but I don't use anything else.
I think what I need on boxes that run 2x7x365 1/4 is a stack of spare hard drives to be swapped at the first sign of trouble
Are you running smartd on them?
Hard drive reliability is still very poor,
Well, what is very poor? Harddrive MTBF (often 1,000,000+ hours) has increased significantly over the last 10-12 years - some manufacturers still provide 5 years warranty, provided you buy server-drives. I have about 25 systems running, including a couple of sub-Tb arrays. The arrays are all SCSI, but there's also a lot of IDE RAID1 arrays about. I think I replace 2, maybe 3 drives per year.
even on big EMC raid subsystems, the most frequent activity is replacing SCSI hard drives, so much so that customers are often left a number of drives so they can replace failing ones themselves.
You're right, of course - but it doesn't say very much about the actual reliability. The number of dead drives per month will always increase with the total number of drives. Also, one thing that'll shorten the lifetime of a drive is temperature. It's worth keeping that server-room nice and cool. /Per Jessen, Zürich, OZ1HZV -- http://www.spamchek.com/freetrial - managed anti-spam and anti-virus solution. Sign up for your free 30-day trial now!
Per Jessen wrote:
Sid Boyce wrote:
On the basis of my troubles over the years, I don't see a reason to switch from reiserfs.
If you (or someoneelse) feel like trying out another journaled filesystem, there's always JFS. I can't actually say if it's any better or not, but I don't use anything else.
I think what I need on boxes that run 2x7x365 1/4 is a stack of spare hard drives to be swapped at the first sign of trouble
Are you running smartd on them?
Yes I am.
Hard drive reliability is still very poor,
Well, what is very poor? Harddrive MTBF (often 1,000,000+ hours) has increased significantly over the last 10-12 years - some manufacturers still provide 5 years warranty, provided you buy server-drives. I have about 25 systems running, including a couple of sub-Tb arrays. The arrays are all SCSI, but there's also a lot of IDE RAID1 arrays about. I think I replace 2, maybe 3 drives per year.
The sites are very large indeed, so may be the numbers as a percentage are quite small, but we were seeing about one or two per month.
even on big EMC raid subsystems, the most frequent activity is replacing SCSI hard drives, so much so that customers are often left a number of drives so they can replace failing ones themselves.
You're right, of course - but it doesn't say very much about the actual reliability. The number of dead drives per month will always increase with the total number of drives.
Also, one thing that'll shorten the lifetime of a drive is temperature. It's worth keeping that server-room nice and cool.
Temperature and humidity on these sites are very closely controlled, it has to be for the amount of equipment installed. Distribution of air to the right places at the correct temperature, humidity and volume is something that is done on preinstallation.
/Per Jessen, Zürich, OZ1HZV
Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Sid Boyce wrote:
The sites are very large indeed, so may be the numbers as a percentage are quite small, but we were seeing about one or two per month.
For a very large system, maybe a large beowulf cluster or similar with 1000s of individual boxes, that sounds entirely reasonable. /Per Jessen, Zürich -- http://www.spamchek.com/freetrial - managed anti-spam and anti-virus solution. Sign up for your free 30-day trial now!
On Sunday 17 July 2005 03:04, Donn Washburn wrote:
You may be correct - but it is my /usr/include directory it is on the same one as my "/" partition. It seems to be working correctly.
File system corruption doesn't have to affect all parts of a file system. It can very well be just one directory, sometimes even just a single file is affected. But usually the only way to fix it is to run an fsck
Anders Johansson wrote:
Classic signs of a corrupted file system. There are ways to deny root permissions on objects, but if you (the administrator) don't know about it, then I can almost guarantee it hasn't been done.
Boot the rescue system and run reiserfsck on your partition (I'm guessing you're running reiser. So far every instance of file system corruption that I've seen that didn't involve a system crash has been in reiser)
You were correct! I shutdown and rebooted and it now works. Shades of Windows - Mouse moved - windows must now reboot" Again Thanks! -- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
On Sat, Jul 16, 2005 at 08:12:45PM -0500, Donn Washburn wrote:
Anders Johansson wrote:
Classic signs of a corrupted file system. There are ways to deny root permissions on objects, but if you (the administrator) don't know about it, then I can almost guarantee it hasn't been done.
Boot the rescue system and run reiserfsck on your partition (I'm guessing you're running reiser. So far every instance of file system corruption that I've seen that didn't involve a system crash has been in reiser)
You were correct! I shutdown and rebooted and it now works. Shades of Windows - Mouse moved - windows must now reboot"
LOL I remember when I saw that joke. Man was it good. "Windows NT has detected you have moved your mouse, please reboot". To stay on topic: BEen using Resiser the two years I've been on Linux. I use it on my I use it on my SUSE boxes, and Slackware, and my server (A PC I souped up and run PureFTPd on) and I've yet to have a problem EVER.
Again Thanks!
-- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On July Sunday 17 2005 1:11 am, Allen wrote:
On Sat, Jul 16, 2005 at 08:12:45PM -0500, Donn Washburn wrote:
Anders Johansson wrote:
Classic signs of a corrupted file system. There are ways to deny root permissions on objects, but if you (the administrator) don't know about it, then I can almost guarantee it hasn't been done.
Boot the rescue system and run reiserfsck on your partition (I'm guessing you're running reiser. So far every instance of file system corruption that I've seen that didn't involve a system crash has been in reiser)
You were correct! I shutdown and rebooted and it now works. Shades of Windows - Mouse moved - windows must now reboot"
Yo! It might have worked this time, but it seems that from 9.0 on there have been major problems w/ ReiserFS .. so let me suggest that if you don't want to change the file systems , and that is understandable, you may at sometime in the future. Not too far distant future wind up w/ a system that *WILL* not boot at all, and may not be recoverable by a simply fsck.. so be Absolutely certain that you have GOOD , SOLID file backups , or you can be crying a lot.. and even Anders won't be able to give you a recovery solution. We have all been thru that stuff , at least once . <very evil grin> IF you have any files you actually really need.. be sure to back them up constantly! Otherwise, you takes your chances in the big computer lottery game ... ;-\ --
participants (7)
-
Allen
-
Anders Johansson
-
Donn Washburn
-
Jeffrey L. Taylor
-
jfweber@bellsouth.net
-
Per Jessen
-
Sid Boyce