Description of problem:

tail -f doesn't work on panassas file systems

It appears like the current rhel6 coreutils blacklists fs's for which inotify doesn't work. These are mostly network file systems. Unfortunately, panassas's file system isn't listed and so tail -f doesn't work.

from tail.c

  886  # if HAVE_FSTATFS && HAVE_STRUCT_STATFS_F_TYPE && defined __linux__
   887    struct statfs buf;
   888    int err = fstatfs (fd, &buf);
   889    if (err != 0)
   890      {
   891        /* On at least linux-2.6.38, fstatfs fails with ENOSYS when FD
   892           is open on a pipe.  Treat that like a remote file.  */
   893        if (errno != ENOSYS)
   894          error (0, errno, _("cannot determine location of %s. "
   895                             "reverting to polling"), quote (name));
   896      }
   897    else
   898      {
   899        switch (buf.f_type)
   900          {
   901          case S_MAGIC_AFS:
   902          case S_MAGIC_CIFS:
   903          case S_MAGIC_CODA:
   904          case S_MAGIC_FUSEBLK:

$ ./f_type /panfs/scratch                                              
  f_type = 0xaad7aaea 

Which seems to be PAN_KERNEL_FS_CLIENT_SUPER_MAGIC

Possible resolution likely seems to be to add PAN_KERNEL_FS_CLIENT_SUPER_MAGIC or 0xaad7aaea to tail's logic.

Version-Release number of selected component (if applicable):
coreutils as shipped with RHEL 6.2

How reproducible:
100%

Steps to Reproduce:
1. Run tail -f against a file on a panassas file system.
2.
3.
  
Actual results:
tail -f does not work

Expected results:
tail -f works

Additional info: