On 07/30/10 13:08, Tim Haley wrote:
When the 'readonly' property is 'on' (read-only) the following actions
are performed:
1). pool is loaded but transaction processing is disabled
2). all filesystems and zvols are mounted in read-only mode
3). any intent-log replays are deferred (any pending synchronous
writes will be replayed once the pool is imported read-write)
What's the behavior with respect to writes to the underlying storage
device(s)?
1) when a pool is imported read-only, are writes ever issued to the
underlying storage? (for instance, for mirror self-healing after a
checksum failure)?
2) is it possible to import, read-only, a pool stored on a
write-protected device or set of devices? (in other words, one which
has to be opened O_RDONLY or equivalent, and/or a device for which all
writes fail?)
- Bill
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
