From: Martin Steigerwald <Martin@lichtvoll.de>
To: jdow <jdow@earthlink.net>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-m68k@vger.kernel.org
Subject: Re: Partitions: Amiga RDB partition on 2 TB disk way too big, while OK in AmigaOS 4.1
Date: Sun, 17 Jun 2012 14:58:58 +0200 [thread overview]
Message-ID: <201206171458.58462.Martin@lichtvoll.de> (raw)
In-Reply-To: <4FDDB667.4020609@earthlink.net>
Am Sonntag, 17. Juni 2012 schrieb jdow:
> I'll have to make time to look it over, considering I am more or less
> the mommy of the RDBs. Now, 2TB may be a tad beyond the abilities of
> the RDBs to express. Memory insists that the RDBs worked on either
> BYTE or block counts. Your seeing a problem at 2TB suggests it really
> stored bit counts. The numbers are supposed to be unsigned. And whether
> the RDBs store values in blocks or BYTEs is immaterial when you get
> down to it. (The RDBs do store the disk's actual and virtual block
> sizes. The latter is what the filesystem uses.)
Hmmm, I thought any 2 TB limit was gone meanwhile, but then your
argumentation has some merit.
Some hints that it might be gone nonetheless:
| JXFS 64 bit file system
|
| With AmigaOS 4.x a new file system has been introduced called JXFS. It is
| a totally new 64 bit file system that supports partitions up to 16 TB in
| size. It is a modern journalling file system, which means that it reduces
| data loss if data writes to the disk are interrupted. It is the fastest
| and most reliable file system ever created for AmigaOS.
http://www.amigaos.net/content/1/features
Well I asked AmigaOS 4 developers about this issue as well. Lets see what
they say about 2 TB limits.
But nonetheless, I think, Linux should refuse to use a partition that is
clearly out of bound.
Scrubbing the one backup BTRFS that has 360 GiB of data was okay. Also the
fsck´s went well. Well the volume group is not completely full so some
space on the end of the disk is not yet used by it.
I am recreating all my backups on BTRFS volumes now - except maybe the one
thats on the BTRFS volume already and scrubs okay.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2012-06-17 12:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 6:41 Partitions: Amiga RDB partition on 2 TB disk way too big, while OK in AmigaOS 4.1 Martin Steigerwald
2012-06-17 8:24 ` Martin Steigerwald
2012-06-17 10:50 ` jdow
2012-06-17 12:58 ` Martin Steigerwald [this message]
2012-06-17 16:36 ` Geert Uytterhoeven
2012-06-17 21:06 ` Martin Steigerwald
2012-06-17 21:58 ` jdow
2012-06-18 21:14 ` Martin Steigerwald
2012-06-17 22:27 ` jdow
2012-06-17 21:06 ` jdow
2012-06-17 21:15 ` Geert Uytterhoeven
2012-06-17 22:09 ` jdow
2012-06-17 21:20 ` Martin Steigerwald
2012-06-17 22:17 ` jdow
2012-06-18 1:28 ` jdow
2012-06-19 19:46 ` Martin Steigerwald
2012-06-18 20:39 ` Martin Steigerwald
2012-06-18 20:58 ` jdow
-- strict thread matches above, loose matches on Subject: below --
2012-06-17 8:33 Martin Steigerwald
2012-06-17 10:53 ` jdow
2012-06-17 12:51 ` Martin Steigerwald
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=201206171458.58462.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=axboe@kernel.dk \
--cc=jdow@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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 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.