From: Wes Janzen <superchkn@sbcglobal.net>
To: Fong Vang <FVang@Zantaz.com>
Cc: reiserfs-list@namesys.com
Subject: Re: root access complains about permission
Date: Thu, 11 Sep 2003 19:24:30 -0500 [thread overview]
Message-ID: <3F61123E.9090809@sbcglobal.net> (raw)
In-Reply-To: <3F60B916.6040408@zantaz.com>
Hi,
I haven't seen anyone post any answers so I'll chip in my 2 cents...
I've seen this when the drive needed fsck to be run. I always got
errors that accompanied this, are you seeing anything in your logs?
I'd be wondering how that happened in the first place though, if this is
the case. I've had an SuSE 8.0 2.4.18 system running for over a year
that's lost power or been reset at least a dozen times without any fs
problems (though I did have to clear out the squid cache). Then again
it wasn't doing much io except writing to the log on a couple
occasions. Still, the only time I had trouble was with my personal
system and that was traced to a hardware problem or a bug in a test
kernel (say 2.6.0-test3).
-Wes-
Fong Vang wrote:
>Any thoughts as to why permission would be denied for root when
>accessing a file on a ReiserFS file system? Here's a sample output
>
>[root@sc15-172-31 log]# id
>
>uid=0(root) gid=0(root)
>groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)
>[root@sc15-172-31 /root]# cd /var/log
>[root@sc15-172-31 log]# ls
>ls: wtmp: Permission denied
>ls: messages: Permission denied
>ls: messages.1: Permission denied
>ls: messages.2: Permission denied
>ls: messages.3: Permission denied
>ls: maillog: Permission denied
>ls: spooler.1: Permission denied
>ls: secure.4: Permission denied
>ls: secure: Permission denied
>ls: maillog.2: Permission denied
>ls: maillog.3: Permission denied
>
>
>kernel is 2.4.19. Reiserfs ver 3.6.25. File system is mounted
>read-write. No ACL. This is a production system that's been up for 2-3
>months. Any help would be appreciated.
>
>
>This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
>service. For more information, visit us at www.zantaz.com.
>IMPORTANT: This electronic mail message is intended only for the use of the
>individual or entity to which it is addressed and may contain information
>that is privileged, confidential or exempt from disclosure under applicable
>law. If the reader of this message is not the intended recipient, or the
>employee or agent responsible for delivering this message to the intended
>recipient, you are hereby notified that any dissemination, distribution or
>copying of this communication is strictly prohibited. If you have received
>this communication in error, please notify the sender immediately by
>telephone or directly reply to the original message(s) sent. Thank you.
>
>
>
next prev parent reply other threads:[~2003-09-12 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 18:04 root access complains about permission Fong Vang
2003-09-12 0:24 ` Wes Janzen [this message]
2003-09-12 9:27 ` Oleg Drokin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F61123E.9090809@sbcglobal.net \
--to=superchkn@sbcglobal.net \
--cc=FVang@Zantaz.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.