[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a52a95e30708091118k1aa962d8u214a7f0624df78e3@mail.gmail.com>
Date: Thu, 9 Aug 2007 11:18:27 -0700
From: "Tom Mortensen" <tmmlkml@...il.com>
To: "Jeff Mahoney" <jeffm@...e.com>
Cc: tony@...rtex.net, linux-kernel@...r.kernel.org,
"ReiserFS Mailing List" <reiserfs-devel@...r.kernel.org>
Subject: Re: reiserfs fs/reiserfs/bitmap.c:1287
Using mkreiserfs version 3.6.19. But file system is less than 80GB.
On 8/8/07, Jeff Mahoney <jeffm@...e.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."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists