mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tom Mortensen" <tmmlkml@gmail.com>
To: "Jeff Mahoney" <jeffm@suse.com>
Cc: tony@tvortex.net, linux-kernel@vger.kernel.org,
	"ReiserFS Mailing List" <reiserfs-devel@vger.kernel.org>
Subject: Re: reiserfs fs/reiserfs/bitmap.c:1287
Date: Thu, 9 Aug 2007 11:18:27 -0700	[thread overview]
Message-ID: <a52a95e30708091118k1aa962d8u214a7f0624df78e3@mail.gmail.com> (raw)
In-Reply-To: <46BA57AC.2040306@suse.com>

Using mkreiserfs version 3.6.19.  But file system is less than 80GB.

On 8/8/07, Jeff Mahoney <jeffm@suse.com> wrote:

> In any event, something is corrupting your bitmaps and that needs to get
> tracked down. The size of the file system is important. I've been seeing
> reports of users hitting similar problems with file systems larger than
> 8 TiB. The cause is that the s_bmap_nr field in the superblock is 16
> bit, and the file system assumes it's correct. mkreiserfs < 3.6.20 will
> happily create those file systems with a value that has wrapped, while
> mkreiserfs >= 3.6.20 will zero the value out, causing a mount failure
> unless the kernel has been patched to support the full size and to
> interpret s_bmap_nr == 0 as "value has overflowed."

      parent reply	other threads:[~2007-08-09 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 17:27 Anthony Simons
2007-07-12 19:14 ` Jeff Mahoney
2007-08-08 22:29   ` Tom Mortensen
2007-08-08 23:43     ` Jeff Mahoney
2007-08-08 23:54     ` Jeff Mahoney
2007-08-09 17:55       ` Tom Mortensen
2007-08-09 18:18       ` Tom Mortensen [this message]

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=a52a95e30708091118k1aa962d8u214a7f0624df78e3@mail.gmail.com \
    --to=tmmlkml@gmail.com \
    --cc=jeffm@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=tony@tvortex.net \
    /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

all inboxes | Powered by JetHome®