From: Chris Worley <chrisw@lnxi.com>
To: reiserfs-list@namesys.com
Subject: Re: Permission denied on access to files; even as root
Date: Sun, 16 Jun 2002 18:47:41 +0000 (UTC) [thread overview]
Message-ID: <1024358539.26879.10782.camel@xserver> (raw)
In-Reply-To: <20020616222011.A15910@namesys.com>
So, If I:
1) compile and install (configured as my previous kernel) the kernel
kernel-source-2.4.16.SuSE-32.i386.rpm at ftp.suse.com in
/pub/suse/i386/update/7.3/2.4.16-20020416 and
2) configure/make/install reiserfsprogs-3.x.1b, and
3) remake my lvm initrd, then
4) reboot single user and run reiserfsck (no args),
I'll have a working, fixed file system that will have large file
capabilities?
Thanks,
Chris
On Sun, 2002-06-16 at 12:20, Oleg Drokin wrote:
> Hello!
>
>
> On Mon, Jun 17, 2002 at 04:50:33PM -0600, Chris Worley wrote:
>
> > I'm Running Linux 2.4.10-4GB on SuSE 7.3 with reiserfsprogs-3.x.0j-1
>
> Consider upgrading your server otherwise problem will repeat itself.
> SuSE update kernel 2.4.16 would be fine for you.
>
> > The problem is progressive. I.e. "/bin/hostname" can't be executed
> > today, and it was fine after trying the "conv".
>
> Yes, newly created files occupy OIDs of already existing ones.
>
> Upgrade kernel and fsck, then run reiserfsck and it will fix the problems.
> 3.x.1b version of reiserfsprogs would be fine for you.
>
> Bye,
> Oleg
>
next prev parent reply other threads:[~2002-06-16 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-16 17:15 Permission denied on access to files; even as root Chris Worley
2002-06-16 17:20 ` Yury Umanets
2002-06-16 17:35 ` Chris Worley
2002-06-16 17:44 ` Yury Umanets
2002-06-16 18:20 ` Oleg Drokin
2002-06-16 18:47 ` Chris Worley [this message]
2002-06-16 23:14 ` Chris Worley
2002-06-17 5:13 ` Oleg Drokin
2002-06-18 6:17 ` Chris Worley
2002-06-17 5:12 ` 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=1024358539.26879.10782.camel@xserver \
--to=chrisw@lnxi.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.