lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <47D0EA6B.18428.A235AEC4@Frantisek.Rysanek.post.cz>
Date:	Fri, 07 Mar 2008 07:10:35 +0100
From:	"Frantisek Rysanek" <Frantisek.Rysanek@...t.cz>
To:	linux-kernel@...r.kernel.org
Subject: Re: block layer / FS question: x86_32bit with LBD, 20 TB RAID volume => funny issues

On 7 Mar 2008 at 4:05, Lee Revell wrote:
> >  I didn't even try Ext3, I know it's not appropriate for this sort of
> >  capacity.
> 
> Where did you get that idea?
>
Hmm... Google can find sources on the 'net claiming that Ext3 has a 
maximum of 2 or 4 TB. Nice to know that I'm wrong, I'll test this 
right away :-)
 
> Are you sure the hardware is not faulty?
>
I'm pretty sure. 
I know what it looks like when one of those 1TB drives has a problem 
it would prefer not to talk about in SMART (hint: only one disk 
activity LED out of 24 keeps blinking). Nowadays I have to handle 
several such drives in every new RAID unit delivered. 
When such a drive times out past some margin, say half a minute, the 
Linux kernel reports a SCSI CMD timeout, or rather, the RAID 
controller runs out of patience sooner than the kernel, the array 
gets degraded and keeps going on in degraded mode. So if the RAID 
controller itself goes out for lunch, Linux definitely complains. 
I've also seen a number of sly SCSI parity errors / general bus 
impedance problems, all of which yielded a proper error within half a 
minute or so. I am well equipped to debug such problems. Besides, 
this is FC. 
Once upon a time I've seen some ugly low-level incompatibility in FC 
too - that resulted in some really nice messages from the Linux 
kernel. 
I also know a brand of controllers which claim support for TCQ depth 
of 255, but actually hang with anything over 192 or so. This also 
yields a proper error in Linux, and the RAID controller goes toes up. 

None of this happens in my case... all is happy and calm.
Hmm... maybe I should try some modern FreeBSD for comparison :-)))

Apologies for not mentioning specific hardware brands - I don't want 
to get in trouble...

> > Would it be any help if I switched to 64bit mode?
> 
> Yes, it would be worth a try.
> 
:-/ Okay, time to install 64bit Fedora 8 or something :-)

Anyway, thanks very much for your response :-)

Frank Rysanek

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ