fdatasync() error in shred from coreutils-5.2.1 on AIX 5.2

[Albert Chin]

I'm running shred from coreutils-5.2.1 on an AIX 5.2 system. /dev/lv00
is a JFS volume:
  $ shred -v /dev/lv00
  /tmp/gshred: /dev/lv00: pass 1/25 (random)...
  /tmp/gshred: /dev/lv00: pass 1/25 (random)...31MiB
  /tmp/gshred: /dev/lv00: fsync: A system call received a parameter that is not 
valid.

The error comes from this portion of src/shred.c:
              /*
               * Force periodic syncs to keep displayed progress accurate
               * FIXME: Should these be present even if -v is not enabled,
               * to keep the buffer cache from filling with dirty pages?
               * It's a common problem with programs that do lots of writes,
               * like mkfs.
               */
              if (fdatasync (fd) < 0 && fsync (fd) < 0)
                { 
                  error (0, errno, "%s: fsync", qname);
                  return -1;
                }

fdatasync(fd) is giving the error. Any ideas?

Based on the following from coreutils.info, the above should work:
     *Please note* that `shred' relies on a very important assumption:
  that the filesystem overwrites data in place.  This is the traditional
  way to do things, but many modern filesystem designs do not satisfy
  this assumption.  Exceptions include:
   
     * Log-structured or journaled filesystems, such as those supplied
       with AIX and Solaris, and JFS, ReiserFS, XFS, Ext3, etc.

  
-- 
albert chin (address@hidden)