On Tue, 29 Dec 2015 20:00:08 -0700 "Gang He" wrote:
> > This feature should be documented, please. That means all pseudo-file
> > locations, all inputs, all outputs, expected behaviour etc etc. Enough
> > info so that our users can usefully and fully use this feature in the
> > minimum time. D
Hello Andrew and Mark,
>>>
> On Fri, 25 Dec 2015 15:16:15 +0800 Gang He wrote:
>
>> When there are errors in the ocfs2 filesystem,
>> they are usually accompanied by the inode number which caused the error.
>> This inode number would be the input to fixing the file.
>> One of these options co
On Fri, 25 Dec 2015 15:16:15 +0800 Gang He wrote:
> When there are errors in the ocfs2 filesystem,
> they are usually accompanied by the inode number which caused the error.
> This inode number would be the input to fixing the file.
> One of these options could be considered:
> A file in the sys
When there are errors in the ocfs2 filesystem,
they are usually accompanied by the inode number which caused the error.
This inode number would be the input to fixing the file.
One of these options could be considered:
A file in the sys filesytem which would accept inode numbers.
This could be used
4 matches
Mail list logo
