Re: Very rough storage validation matrix draft

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2014-03-17 at 10:25 -0400, Al Dunsmuir wrote:
> On Monday, March 17, 2014, 4:14:50 AM, Kamil Paral wrote:
> > I can't either, and even if I did, I don't think it would justify
> > the result number explosion. Storage is storage, arch is usually completely irrelevant.
> 
> > When we're at it, why do we have both i686 and x86_64 at "Device
> > tests"? A single results column for x86 should be enough. Same reasoning.
> 
> In  the  past, some filesystems have had issues handling 64-bit inodes
> in  32-bit  architectures.  User  data  is  too  important  to make an
> assumption that these no longer will occur.

Device tests are not filesystem tests, though.

Could you provide some references to these issues?

With either set of tests, though, I don't see that any 'user data' is
involved: in each case the only partitions we're creating or touching
are new ones with no user data involved. Even if one of the filesystems
we create might suffer from a bug further down the line, I don't think
any of these tests would catch it, would they?
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test





[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux