On Thu, Dec 07, 2017 at 07:21:46AM -0500, Austin S. Hemmelgarn wrote:
> On 2017-12-07 06:55, Duncan wrote:
> >Misono, Tomohiro posted on Thu, 07 Dec 2017 16:15:47 +0900 as excerpted:
> >
> >>On 2017/12/07 11:56, Duncan wrote:
> >>>Austin S. Hemmelgarn posted on Wed, 06 Dec 2017 07:39:56 -0500 as
>
On 2017-12-07 06:55, Duncan wrote:
Misono, Tomohiro posted on Thu, 07 Dec 2017 16:15:47 +0900 as excerpted:
On 2017/12/07 11:56, Duncan wrote:
Austin S. Hemmelgarn posted on Wed, 06 Dec 2017 07:39:56 -0500 as
excerpted:
Somewhat OT, but the only operation that's remotely 'instant' is
On 2017年12月07日 15:32, Marat Khalili wrote:
> On 07/12/17 08:27, Qu Wenruo wrote:
>> When doing snapshot, btrfs only needs to increase reference of 2nd
>> highest level tree blocks of original snapshot, other than "walking the
>> tree".
>> (If tree root level is 2, then level 2 node is copied,
On 07/12/17 08:27, Qu Wenruo wrote:
When doing snapshot, btrfs only needs to increase reference of 2nd
highest level tree blocks of original snapshot, other than "walking the
tree".
(If tree root level is 2, then level 2 node is copied, while all
reference of level 1 tree blocks get increased)
On 2017/12/07 11:56, Duncan wrote:
> Austin S. Hemmelgarn posted on Wed, 06 Dec 2017 07:39:56 -0500 as
> excerpted:
>
>> Somewhat OT, but the only operation that's remotely 'instant' is
>> creating an empty subvolume. Snapshot creation has to walk the tree in
>> the subvolume being snapshotted,
On 2017年12月06日 20:39, Austin S. Hemmelgarn wrote:
> Somewhat OT, but the only operation that's remotely 'instant' is
> creating an empty subvolume. Snapshot creation has to walk the tree in
> the subvolume being snapshotted, which can take a long time (and as a
> result of it's implementation,
Austin S. Hemmelgarn posted on Wed, 06 Dec 2017 07:39:56 -0500 as
excerpted:
> Somewhat OT, but the only operation that's remotely 'instant' is
> creating an empty subvolume. Snapshot creation has to walk the tree in
> the subvolume being snapshotted, which can take a long time (and as a
>
On 2017-12-05 23:52, Misono, Tomohiro wrote:
On 2017/12/05 21:41, Austin S. Hemmelgarn wrote:
On 2017-12-05 03:43, Qu Wenruo wrote:
On 2017年12月05日 16:25, Misono, Tomohiro wrote:
Hello all,
I want to address some issues of subvolume usability for a normal user.
i.e. a user can create
On 2017-12-05 17:08, Goffredo Baroncelli wrote:
On 12/05/2017 09:17 PM, Austin S. Hemmelgarn wrote:
On 2017-12-05 14:09, Goffredo Baroncelli wrote:
On 12/05/2017 07:46 PM, Graham Cobb wrote:
On 05/12/17 18:01, Goffredo Baroncelli wrote:
On 12/05/2017 04:42 PM, Graham Cobb wrote:
[]
On 2017/12/05 21:41, Austin S. Hemmelgarn wrote:
> On 2017-12-05 03:43, Qu Wenruo wrote:
>>
>>
>> On 2017年12月05日 16:25, Misono, Tomohiro wrote:
>>> Hello all,
>>>
>>> I want to address some issues of subvolume usability for a normal user.
>>> i.e. a user can create subvolumes, but
>>> - Cannot
On 12/05/2017 09:17 PM, Austin S. Hemmelgarn wrote:
> On 2017-12-05 14:09, Goffredo Baroncelli wrote:
>> On 12/05/2017 07:46 PM, Graham Cobb wrote:
>>> On 05/12/17 18:01, Goffredo Baroncelli wrote:
On 12/05/2017 04:42 PM, Graham Cobb wrote:
>> []
>>> Then no impact to kernel, all
On 2017-12-05 14:09, Goffredo Baroncelli wrote:
On 12/05/2017 07:46 PM, Graham Cobb wrote:
On 05/12/17 18:01, Goffredo Baroncelli wrote:
On 12/05/2017 04:42 PM, Graham Cobb wrote:
[]
Then no impact to kernel, all complex work is done in user space.
Exactly how hard is it to just check
On 12/05/2017 07:46 PM, Graham Cobb wrote:
> On 05/12/17 18:01, Goffredo Baroncelli wrote:
>> On 12/05/2017 04:42 PM, Graham Cobb wrote:
[]
> Then no impact to kernel, all complex work is done in user space.
Exactly how hard is it to just check ownership of the root inode of a
On 05/12/17 18:01, Goffredo Baroncelli wrote:
> On 12/05/2017 04:42 PM, Graham Cobb wrote:
>> On 05/12/17 12:41, Austin S. Hemmelgarn wrote:
>>> On 2017-12-05 03:43, Qu Wenruo wrote:
On 2017年12月05日 16:25, Misono, Tomohiro wrote:
> Hello all,
>
> I want to address some
On 12/05/2017 09:25 AM, Misono, Tomohiro wrote:
> Hello all,
>
> I want to address some issues of subvolume usability for a normal user.
> i.e. a user can create subvolumes, but
> - Cannot delete their own subvolume (by default)
> - Cannot tell subvolumes from directories (in a straightforward
On 12/05/2017 04:42 PM, Graham Cobb wrote:
> On 05/12/17 12:41, Austin S. Hemmelgarn wrote:
>> On 2017-12-05 03:43, Qu Wenruo wrote:
>>>
>>>
>>> On 2017年12月05日 16:25, Misono, Tomohiro wrote:
Hello all,
I want to address some issues of subvolume usability for a normal user.
i.e.
On 05/12/17 12:41, Austin S. Hemmelgarn wrote:
> On 2017-12-05 03:43, Qu Wenruo wrote:
>>
>>
>> On 2017年12月05日 16:25, Misono, Tomohiro wrote:
>>> Hello all,
>>>
>>> I want to address some issues of subvolume usability for a normal user.
>>> i.e. a user can create subvolumes, but
>>> - Cannot
On 2017-12-05 03:43, Qu Wenruo wrote:
On 2017年12月05日 16:25, Misono, Tomohiro wrote:
Hello all,
I want to address some issues of subvolume usability for a normal user.
i.e. a user can create subvolumes, but
- Cannot delete their own subvolume (by default)
- Cannot tell subvolumes from
On 2017年12月05日 16:25, Misono, Tomohiro wrote:
> Hello all,
>
> I want to address some issues of subvolume usability for a normal user.
> i.e. a user can create subvolumes, but
> - Cannot delete their own subvolume (by default)
> - Cannot tell subvolumes from directories (in a straightforward
19 matches
Mail list logo
