public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: ak@suse.de
Subject: [Bug 1083] New: JFS corrupts file systems on 64bit architectures
Date: Mon, 11 Aug 2003 13:14:58 -0700	[thread overview]
Message-ID: <872950000.1060632898@flay> (raw)

http://bugme.osdl.org/show_bug.cgi?id=1083

           Summary: JFS corrupts file systems on 64bit architectures
    Kernel Version: 2.6.0test2
            Status: NEW
          Severity: high
             Owner: shaggy@austin.ibm.com
         Submitter: ak@suse.de


On AMD64 JFS seems to corrupt file systems quickly. I created a JFS
file system, rsync'ed an BKCVS kernel checkout from another box then
did two cvs updates. Result was that several directory inodes in the 
kernel tree were unreadable on the next access (always returned EPERM 
even for a stat). I did a fsck then, which found some bad inodes and 
resulted in a endless lost+found (ls ran out of memory trying to list it)

2.4 JFS still worked. I also got feedback from one user that they are
seeing similar problems on sparc64.



                 reply	other threads:[~2003-08-11 20:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=872950000.1060632898@flay \
    --to=mbligh@aracnet.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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