Discussion:
bug#14251: coreutils-8.15: tail.c : Need support for StorNext file system as distributed file system
(too old to reply)
Guenter Ressel-Herbert
2013-04-24 06:47:19 UTC
Permalink
Folks,

my name is Guenter Ressel-Herbert and I'm working in Quantum's StorNext Sustaining Engineering team.
I have a customer that needs support for tail -f on our StorNext SAN clients. StorNext (ex cvfs) is a distributed
file system that is bypassing the VFS layer on the client, hence no trigger for any inotify registration. Seems to
be a common issue for most distributed file systems. Checking out coreutils-8.15/src/tail.c, I found that
tail -f reverts back to the traditional polling method for all FS's listed in src/fs-is-local.h returning 0. Would
you please be so kind and add StorNext as distributed file system to that header file? You also might need
to make up a new #define for the StorNext magic listed below.

StorNext output for fstatfs:




fstatfs(3, {f_type=0xbeefdead, f_bsize=4096, f_blocks=244187136, f_bfree=242457823, f_bavail=242457823, f_files=1262592, f_ffree=1262483, f_fsid={1939504002, 317934}, f_namelen=255, f_frsize=4096}) = 0



As you see, the magic is 0xbeefdead.



Thanks a lot!



Guenter Ressel-Herbert







----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.
Pádraig Brady
2013-04-24 22:08:20 UTC
Permalink
Post by Guenter Ressel-Herbert
Folks,
my name is Guenter Ressel-Herbert and I'm working in Quantum's StorNext Sustaining Engineering team.
I have a customer that needs support for tail -f on our StorNext SAN clients. StorNext (ex cvfs) is a distributed
file system that is bypassing the VFS layer on the client, hence no trigger for any inotify registration. Seems to
be a common issue for most distributed file systems. Checking out coreutils-8.15/src/tail.c, I found that
tail -f reverts back to the traditional polling method for all FS's listed in src/fs-is-local.h returning 0. Would
you please be so kind and add StorNext as distributed file system to that header file? You also might need
to make up a new #define for the StorNext magic listed below.
fstatfs(3, {f_type=0xbeefdead, f_bsize=4096, f_blocks=244187136, f_bfree=242457823, f_bavail=242457823, f_files=1262592, f_ffree=1262483, f_fsid={1939504002, 317934}, f_namelen=255, f_frsize=4096}) = 0
As you see, the magic is 0xbeefdead.
While I'm slightly hesitant above adding support for
this closed source file system, there is precedence,
and I see the clients are GPL.

So I propose to support this with the attached.

thanks,
Pádraig.
Jim Meyering
2013-04-25 04:04:19 UTC
Permalink
Subject: [PATCH] stat,tail: improve support for snfs
The StorNext distributed file system was previously known as CVFS.
* src/stat.c (human_fstype): Add new file system ID definition.
* NEWS: Mention the improvement.
Fixes http://bugs.gnu.org/14251
Looks fine. Thanks.`
Bernhard Voelker
2013-04-25 07:15:25 UTC
Permalink
Post by Pádraig Brady
While I'm slightly hesitant above adding support for
this closed source file system, there is precedence,
and I see the clients are GPL.
So I propose to support this with the attached.
Hi Padraig,

I also searched a bit for 0xBEEFDEAD, but I couldn't find
a good document related to StorNext. Where did you find
the file system name? Should we add such an URL to the commit?

Otherwise, the patch looks good.

Have a nice day,
Berny
Pádraig Brady
2013-04-25 08:53:08 UTC
Permalink
Post by Bernhard Voelker
Post by Pádraig Brady
While I'm slightly hesitant above adding support for
this closed source file system, there is precedence,
and I see the clients are GPL.
So I propose to support this with the attached.
Hi Padraig,
I also searched a bit for 0xBEEFDEAD, but I couldn't find
a good document related to StorNext. Where did you find
the file system name? Should we add such an URL to the commit?
I got the name from just searching for snfs and cvfs.
There were various URLs referring to both.

As for BEEFDEAD, I didn't see anything online.
Guenter, can you post a link to the GPL client code
so we can link/verify?
Post by Bernhard Voelker
Otherwise, the patch looks good.
thanks,
Pádraig.
Pádraig Brady
2013-04-25 16:05:43 UTC
Permalink
Post by Pádraig Brady
Post by Bernhard Voelker
Post by Pádraig Brady
While I'm slightly hesitant above adding support for
this closed source file system, there is precedence,
and I see the clients are GPL.
So I propose to support this with the attached.
Hi Padraig,
I also searched a bit for 0xBEEFDEAD, but I couldn't find
a good document related to StorNext. Where did you find
the file system name? Should we add such an URL to the commit?
I got the name from just searching for snfs and cvfs.
There were various URLs referring to both.
As for BEEFDEAD, I didn't see anything online.
Guenter, can you post a link to the GPL client code
so we can link/verify?
Sorry I got confused with FhGFS, which has GPL clients.

thanks,
Pádraig.

Loading...