Wouldn't that be:
5 seconds per write = 86400/5 = 17280 writes per day
256 rotated locations for 17280/256 = 67 writes per location per day
Resulting in (100000/67) ~1492 days or 4.08 years before failure?
That's still a long time, but it's not 100 years.
On Jun 20, 2006, at 12:47 PM, Eric Schrock wrote:
On Tue, Jun 20, 2006 at 11:17:42AM -0700, Jonathan Adams wrote:
On Tue, Jun 20, 2006 at 09:32:58AM -0700, Richard Elling wrote:
Flash is (can be) a bit more sophisticated. The problem is that
they
have a limited write endurance -- typically spec'ed at 100k
writes to
any single bit. The good flash drives use block relocation,
spares, and
write spreading to avoid write hot spots. For many file systems,
the
place to worry is the block(s) containing your metadata. ZFS
inherently
spreads and mirrors its metadata, so it should be more
appropriate for
flash devices than FAT or UFS.
What about the UberBlock? It's written each time a transaction group
commits.
Yes, but this is only written once every 5 seconds, and we store to
256
different locations in a ring buffer. So you have (256*100000*5)
seconds, or about 100 years.
- Eric
--
Eric Schrock, Solaris Kernel Development http://blogs.sun.com/
eschrock
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
-----
Gregory Shaw, IT Architect
Phone: (303) 673-8273 Fax: (303) 673-2773
ITCTO Group, Sun Microsystems Inc.
1 StorageTek Drive ULVL4-382 [EMAIL PROTECTED] (work)
Louisville, CO 80028-4382 [EMAIL PROTECTED] (home)
"When Microsoft writes an application for Linux, I've Won." - Linus
Torvalds
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
