I tried the patch, same problem show up, but no bug_on report Is there any other things I can do? Jeff > Yes, I meant 2T, and yes, the components are always over 2T. > So I'm at a complete loss. The raid0 code follows the same > paths and does the same things and uses 64bit arithmetic where needed. > > So I have no idea how there could be a difference between > these two cases. > > I'm at a loss... > > NeilBrown > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Software raid0 will crash the file-system, when each disk is 5TB
- From: "Jeff Zheng" <[email protected]>
- Re: Software raid0 will crash the file-system, when each disk is 5TB
- From: "Michal Piotrowski" <[email protected]>
- Re: Software raid0 will crash the file-system, when each disk is 5TB
- From: Neil Brown <[email protected]>
- RE: Software raid0 will crash the file-system, when each disk is 5TB
- From: "Jeff Zheng" <[email protected]>
- RE: Software raid0 will crash the file-system, when each disk is 5TB
- From: Neil Brown <[email protected]>
- RE: Software raid0 will crash the file-system, when each disk is 5TB
- From: "Jeff Zheng" <[email protected]>
- RE: Software raid0 will crash the file-system, when each disk is 5TB
- From: Neil Brown <[email protected]>
- Software raid0 will crash the file-system, when each disk is 5TB
- Prev by Date: Re: 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64
- Next by Date: Re: [PATCH] recalc_sigpending_tsk fixes
- Previous by thread: RE: Software raid0 will crash the file-system, when each disk is 5TB
- Next by thread: RE: Software raid0 will crash the file-system, when each disk is 5TB
- Index(es):
 |