From: Andries Brouwer <aebr@win.tue.nl>
To: steveb@unix.lancs.ac.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: corruption with A7A266+200GB disk?
Date: Tue, 2 Sep 2003 23:55:43 +0200 [thread overview]
Message-ID: <20030902235543.B1627@pclin040.win.tue.nl> (raw)
In-Reply-To: <E19uBCi-00054b-00@wing0.lancs.ac.uk>; from steveb@unix.lancs.ac.uk on Tue, Sep 02, 2003 at 02:28:16PM +0100
On Tue, Sep 02, 2003 at 02:28:16PM +0100, steveb@unix.lancs.ac.uk wrote:
> I just got a new 200GB disk (WDC WD2000JB) for my home machine (Asus A7A266,
> Ali chipset). I put some partitions on it like so:
> hda1: 100MB - /boot
> hda2: 8192MB - /
> hda3: 1024MB - swap
> hda4: the rest (about 190GB I guess) - /home
>
> I find that when I mkfs on /home, I get massive filesystem corruption on /
> When I fsck / (and restore the deleted files) I get massive filesystem corruption on /home.
>
> so...anyone else seen this? Is it a known driver problem?
No doubt wraparound at 137 GB. (2^28 sectors of 2^9 bytes gives a 2^37 byte,
that is 128 GiB limit; to get past this you need support for lba48)
Recently we discussed a case where Linux decided that the hardware
could not handle lba48 but forgot to adapt the total capacity.
That was a Linux bug.
In fact, if I am not mistaken, the idea that that hardware could not
handle lba48 was due to a misunderstanding. That was another Linux bug.
Maybe these have now been fixed in some kernel versions.
So, you must check (i) what Linux thinks your hardware can do, and
(ii) what your hardware can do in reality.
Maybe the former can be seen in /proc/ide/hdX/settings under "address"
or so.
next prev parent reply other threads:[~2003-09-02 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 13:28 steveb
2003-09-02 21:55 ` Andries Brouwer [this message]
2003-09-03 0:55 ` Bartlomiej Zolnierkiewicz
2003-09-03 13:35 ` Alan Cox
2003-09-05 9:43 ` Steve Bennett
2003-09-05 11:42 ` Dave Gilbert (Home)
2003-09-03 1:37 ` Erik Andersen
2003-09-03 18:07 ` Marcelo Tosatti
2003-09-03 18:27 ` Alan Cox
2003-09-03 19:54 ` Marcelo Tosatti
2003-09-03 20:06 ` Erik Andersen
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=20030902235543.B1627@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=steveb@unix.lancs.ac.uk \
/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®