On 07/30/2016 01:14 AM, Goffredo Baroncelli wrote:
On 2016-07-29 08:44, Qu Wenruo wrote:
On 07/29/2016 01:08 PM, Goffredo Baroncelli wrote:
On 2016-07-29 03:34, Qu Wenruo wrote:
I am not against about your proposal; however I have to point
out that the goal of these command was not to
On 2016-07-29 08:44, Qu Wenruo wrote:
>
>
> On 07/29/2016 01:08 PM, Goffredo Baroncelli wrote:
>> On 2016-07-29 03:34, Qu Wenruo wrote:
I am not against about your proposal; however I have to point
out that the goal of these command was not to *traverse* the
file, but only to
On 07/29/2016 01:08 PM, Goffredo Baroncelli wrote:
On 2016-07-29 03:34, Qu Wenruo wrote:
I am not against about your proposal; however I have to point out
that the goal of these command was not to *traverse* the file, but
only to found the physical location of a file offset. My use case
was
On 2016-07-29 03:34, Qu Wenruo wrote:
>> I am not against about your proposal; however I have to point out
>> that the goal of these command was not to *traverse* the file, but
>> only to found the physical location of a file offset. My use case
>> was to simulate a corruption of a raid5 stripe
Hi, Goffredo,
Sorry I forgot to mention that, even btrfs-map-logcal is an offline
tool, it can still handle mount fs too.
Although it's also true that it still lacks the needed RAID flags and
stripe info.
At 07/29/2016 04:25 AM, Goffredo Baroncelli wrote:
Hi Qu,
On 2016-07-28 03:47, Qu
Hi Qu,
On 2016-07-28 03:47, Qu Wenruo wrote:
> At 07/28/2016 01:43 AM, Goffredo Baroncelli wrote:
>> From: Goffredo Baroncelli
>>
>> The aim of this new command is to show the physical placement on the disk
>> of a file.
>> Currently it handles all the profiles (single, dup,
At 07/28/2016 01:43 AM, Goffredo Baroncelli wrote:
From: Goffredo Baroncelli
The aim of this new command is to show the physical placement on the disk
of a file.
Currently it handles all the profiles (single, dup, raid1/10/5/6).
The syntax is simple:
Uh...
Where is the
From: Goffredo Baroncelli
The aim of this new command is to show the physical placement on the disk
of a file.
Currently it handles all the profiles (single, dup, raid1/10/5/6).
The syntax is simple:
where:
is the file to inspect
is the offset of the file to inspect
From: Goffredo Baroncelli
The aim of this new command is to show the physical placement on the disk
of a file.
Currently it handles all the profiles (single, dup, raid1/10/5/6).
The syntax is simple:
where:
is the file to inspect
is the offset of the file to inspect