r,
> I had to solve the same "inode" issue that you met. This solution as very
> few impact on nfs-ganesha code (it just adds a new FSAL).
>
> Regards
>
> Philippe
>
> On 01/03/18 19:58, Aurelien RAINONE wrote:
>
> To follow up on the developme
On 3 Jan 2018 21:02, "Frank Filz" wrote:
> From: Aurelien RAINONE [mailto:aurelien.rain...@gmail.com]
> Sent: Wednesday, January 3, 2018 10:58 AM
> To: Nfs-ganesha-devel@lists.sourceforge.net
> Subject: [Nfs-ganesha-devel] Implement a FSAL for S3-compatible storage
&
To follow up on the development on an FSAL for S3, I have some doubts
and questions I'd like to share.
Apart from its full path, S3 doesn't have the concept of file
descriptor, I mean, there's nothing else
than the full path that I can provide to S3 in order to get attribute
of content of a spec
Hi,
I'm new to nfs-ganesha and on this mailing-list. I'm currently reading a
maximum of documentation and code in order to understand where to start the
implementation of a new FSAL.
The main objectives of my development are:
- connect one fsal export to exactly one S3 Bucket. Requests to the S3
