Turns out, because it was an untar of the OneFS 6.5.5.29 installation tarball, there were some files that had special flags set (chflags(1)). There were visible with the 'ls -lo' command.  Someone guided me in the right direction in the Isilon Users Google Group.  # cd /ifs/data # chflags -R 0 bin lib libexec sbin usr var # rm -r bin lib libexec sbin usr var #
I'm stumped. Has anyone seen this before? What am I doing wrong? I un-packaged the OneFS 6.5.5.29 tarball (I didn't realize yet that it was supposed to be left intact) in /ifs/data and now want to clean all of that up. I'm left with various directories and files, like the one below, that give me "Operation not permitted" when I try to rm them.  isibed-1# pwd /ifs/data isibed-1# ls -led . drwxr-xr-x    9 root  wheel  203 Dec 24 15:21 .  OWNER: user:root  GROUP: group:wheel  SYNTHETIC ACL  0: user:root allow dir_gen_read,dir_gen_write,dir_gen_execute,std_write_dac,delete_child  1: group:wheel allow dir_gen_read,dir_gen_execute  2: everyone allow dir_gen_read,dir_gen_execute isibed-1# ls -led bin drwxrwxrwx    2 root  wheel  21 Dec 24 15:20 bin  OWNER: user:root  GROUP: group:wheel  SYNTHETIC ACL  0: user:root allow dir_gen_read,dir_gen_write,dir_gen_execute,std_write_dac,delete_child  1: group:wheel allow dir_gen_read,dir_gen_write,dir_gen_execute,delete_child  2: everyone allow dir_gen_read,dir_gen_write,dir_gen_execute,delete_child isibed-1# ls -led bin/rcp -rwxrwxrwx    1 root  wheel  44256 Jun 10 2014 bin/rcp  OWNER: user:root  GROUP: group:wheel  SYNTHETIC ACL  0: user:root allow file_gen_read,file_gen_write,file_gen_execute,std_write_dac  1: group:wheel allow file_gen_read,file_gen_write,file_gen_execute  2: everyone allow file_gen_read,file_gen_write,file_gen_execute isibed-1# rm bin/rcp remove bin/rcp? y rm: bin/rcp: Operation not permitted isibed-1#
OneFS rm - Operation not permitted