In the last month - definitely after going to 5.5 - I've tried to fsck a
drive (340 days, or some such, unchecked). 960G RAID 5, I *think*,
possibly serial port attachment to a JetStore RAID array. Every time I
try, it gets to 70.0%, and stops. As in, I left it run last night, having
started it
On Tue, Jul 20, 2010 at 1:57 PM, m.r...@5-cent.us wrote:
Note that my manager tried to run one on another server, also attached to
a JetStore, and it also stopped at the exact same point. This has never
happened before, and fsck has handled these in the past.
Anyone seen anything like this,
On 07/20/2010 10:57 AM, m.r...@5-cent.us wrote:
In the last month - definitely after going to 5.5 - I've tried to fsck a
drive (340 days, or some such, unchecked). 960G RAID 5, I *think*,
possibly serial port attachment to a JetStore RAID array. Every time I
try, it gets to 70.0%, and stops.
On Tue, Jul 20, 2010 at 11:10:45AM -0700, Benjamin Franz wrote:
I've seen e2fsck hang on large arrays (terabyte range) before,
particularly if you have lots of hard links. It's a bug in fsck.
I've see that too. Glad it's not just on my systems ... sorta.
Whit
Kwan Lowe wrote:
On Tue, Jul 20, 2010 at 1:57 PM, m.r...@5-cent.us wrote:
Note that my manager tried to run one on another server, also attached
to
a JetStore, and it also stopped at the exact same point. This has never
happened before, and fsck has handled these in the past.
Anyone seen
Benjamin Franz wrote:
On 07/20/2010 10:57 AM, m.r...@5-cent.us wrote:
In the last month - definitely after going to 5.5 - I've tried to fsck a
drive (340 days, or some such, unchecked). 960G RAID 5, I *think*,
possibly serial port attachment to a JetStore RAID array. Every time I
try, it gets
6 matches
Mail list logo
