Re: Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)

2010-11-30 Thread Andrey Kuzmin
In my opinion, the point is not the default snapshot creation mode but rather default usage, equals user's expectation. On 11/30/10, Li Zefan wrote: > C Anthony Risinger wrote: >> On Nov 29, 2010, at 3:48 PM, Andrey Kuzmin >> wrote: >> >>> I'm not sure why zfs came up, they don't own the term :)

Re: Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)

2010-11-29 Thread Li Zefan
C Anthony Risinger wrote: > On Nov 29, 2010, at 3:48 PM, Andrey Kuzmin > wrote: > >> I'm not sure why zfs came up, they don't own the term :). As to >> zfs/overhead topic, I doubt there's any difference between clone and >> writable shapshot (there should be none, of course, it's just two >> diff

Re: Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)

2010-11-29 Thread C Anthony Risinger
On Nov 29, 2010, at 3:48 PM, Andrey Kuzmin wrote: > I'm not sure why zfs came up, they don't own the term :). As to > zfs/overhead topic, I doubt there's any difference between clone and > writable shapshot (there should be none, of course, it's just two > different names for the same concept). >

Re: Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)

2010-11-29 Thread Andrey Kuzmin
I'm not sure why zfs came up, they don't own the term :). As to zfs/overhead topic, I doubt there's any difference between clone and writable shapshot (there should be none, of course, it's just two different names for the same concept). Regards, Andrey On Tue, Nov 30, 2010 at 12:43 AM, Mike F

Re: Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)

2010-11-29 Thread Mike Fedyk
On Mon, Nov 29, 2010 at 1:31 PM, Andrey Kuzmin wrote: > This may sound excessive as any new concept introduction that late in > development, but readonly/writable snapshots could be further > differentiated by naming the latter clones. This way end-user would > naturally perceive snapsot as read-o

Re: Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)

2010-11-29 Thread Andrey Kuzmin
This may sound excessive as any new concept introduction that late in development, but readonly/writable snapshots could be further differentiated by naming the latter clones. This way end-user would naturally perceive snapsot as read-only PIT fs image, while clone would naturally refer to (writabl

Re: Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)

2010-11-29 Thread Mike Fedyk
On Mon, Nov 29, 2010 at 12:41 PM, David Arendt wrote: > On 11/29/10 21:02, Mike Fedyk wrote: >> >> On Mon, Nov 29, 2010 at 12:02 AM, Li Zefan  wrote: >>> >>> (Cc: Sage Weil  for changes in async snapshots) >>> >>> This patchset adds readonly-snapshots support. You can create a >>> readonly snapsho

Re: Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)

2010-11-29 Thread David Arendt
On 11/29/10 21:02, Mike Fedyk wrote: On Mon, Nov 29, 2010 at 12:02 AM, Li Zefan wrote: (Cc: Sage Weil for changes in async snapshots) This patchset adds readonly-snapshots support. You can create a readonly snapshot, and you can also set a snapshot readonly/writable on the fly. A few readonl

Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)

2010-11-29 Thread Mike Fedyk
On Mon, Nov 29, 2010 at 12:02 AM, Li Zefan wrote: > (Cc: Sage Weil for changes in async snapshots) > > This patchset adds readonly-snapshots support. You can create a > readonly snapshot, and you can also set a snapshot readonly/writable > on the fly. > > A few readonly checks are added in setatt