public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Diego Calleja <grundig@teleline.es>
To: Hans Reiser <reiser@namesys.com>
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: [reiserfs-list] Re: Reiserfs corruption on 2.4.17-rc1!
Date: Tue, 18 Dec 2001 22:35:40 +0100	[thread overview]
Message-ID: <20011218223540.A377@diego> (raw)
In-Reply-To: <20011217025856.A1649@diego> <13425.1008580831@nova.botz.org> <20011218003359.A555@diego> <15391.12150.650359.33792@laputa.namesys.com> <3C1F3FDA.5050601@namesys.com>
In-Reply-To: <3C1F3FDA.5050601@namesys.com>; from reiser@namesys.com on Tue, Dec 18, 2001 at 14:08:42 +0100


On Tue, 18 Dec 2001 14:08:42 Hans Reiser wrote:
> Nikita Danilov wrote:
> 
> >Diego Calleja writes:
> >
> >
> >Unfortunately this looks like "standard" reiserfs tree corruption. 
> >Take
> >
> A little more precisely: nobody at Namesys has ever hit this bug using 
> our known healthy hardware.  Various users have.  Bad hardware (e.g 
> media defect) could cause this bug, and maybe cause it in just about the 
> number of users that we see it in.   This does NOT mean that it is due 
> to bad hardware.  If you, or anyone, can reproduce this bug, we would be 
> very interested to learn how to do so.
> 
> Hans
I'm afraid I can't. It just happened. I only can describe what was I doing,
although it must be useless....
The system booted with linux 2.4.17-rc1. I was readin mail in kde
 when  I tried to mount my vfat partition on /win to listen mp3. (as a
normal
 user, of course). But  I couldn't mount it. Reason?:
 	ls: mtab: permission denied
 Then I log as root, but ls -l /etc/mtab said:
 	ls: mtab: permission denied
 any chmod in /etc/mtab: (as root)
 	chmod: getting attributes of mtab: Permission denied

 After this, the filesystem started to fail a lot in all other programs
 , the problem is in some files in /etc.



  parent reply	other threads:[~2001-12-18 21:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-16 17:48 Reiserfs corruption on 2.4.17-rc1! Diego Calleja
2001-12-16 17:57 ` Diego Calleja
2001-12-16 20:12 ` Ragnar Kjørstad
2001-12-17  1:58   ` Diego Calleja
2001-12-17 21:01     ` Sakari Ailus
     [not found]     ` <13425.1008580831@nova.botz.org>
2001-12-17 23:33       ` Diego Calleja
2001-12-18  5:01         ` Ross Vandegrift
2001-12-18  6:19           ` Jurgen Botz
2001-12-18 21:45           ` Diego Calleja
     [not found]         ` <15391.12150.650359.33792@laputa.namesys.com>
     [not found]           ` <20011218220828.A381@diego>
2001-12-18 21:11             ` [grundig@teleline.es: Re: Reiserfs corruption on 2.4.17-rc1!] Diego Calleja
2001-12-19  9:18               ` Nikita Danilov
     [not found]           ` <3C1F3FDA.5050601@namesys.com>
2001-12-18 21:35             ` Diego Calleja [this message]
     [not found]         ` <20011218125852.A1159@namesys.com>
     [not found]           ` <20011218224848.C377@diego>
     [not found]             ` <20011219095303.A11409@namesys.com>
2001-12-20  0:20               ` Reiserfs corruption on 2.4.17-rc1! Diego Calleja
     [not found] <200112190118.fBJ1IHb92286@spf5.us4.outblaze.com>
2001-12-19 20:23 ` [reiserfs-list] " Asheesh Laroia

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=20011218223540.A377@diego \
    --to=grundig@teleline.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox