Does VMLINK with the NONAMES option cause the same behavior? VMLINK user disk (NON
I'm not sure about in this case, but NAMES files can sometimes create problems when using VMLINK - so I tend to use NONames Scott Rohling On Tue, Apr 19, 2011 at 2:08 PM, Alain Benveniste <a.benveni...@free.fr>wrote: > I executed this exec : > /**/ > "VMLINK 5VMDIR40 0491" > "VMLINK 5VMDIR40 0492" > "VMLINK 5VMDIR40 011F" > "VMLINK 5VMDIR40 041F" > "VMLINK DIRMAINT 01AA" > "VMLINK DIRMAINT 01FA" > "VMLINK DIRMAINT 02AA" > "VMLINK DIRMAINT 0155" > "VMLINK DIRMAINT 01DF" > > > DMSACC048E Invalid filemode S > Ready(02024); T=0.01/0.01 16:05:35 > > I received DMSACC048E Invalid filemode S for the VMLINK DIRMAINT 01DF > > q disk > LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK > TOTAL > MNT191 191 A R/W 175 3390 4096 121 1459-05 30041 > 31500 > MNT190 190 S R/O 100 3390 4096 704 15293-85 2707 > 18000 > DIR155 127 T R/O 9 3390 4096 10 23-01 1597 > 1620 > DIR1AA 126 U R/O 9 3390 4096 6 13-01 1607 > 1620 > DRM41F 125 V R/O 8 3390 4096 50 642-45 798 > 1440 > DIR11F 124 W R/O 15 3390 4096 49 629-23 2071 > 2700 > DRM492 121 X R/O 15 3390 4096 269 1490-55 1210 > 2700 > MNT19E 19E Y/S R/O 250 3390 4096 1779 38956-87 6044 > 45000 > DRM491 120 Z R/O 15 3390 4096 259 1410-52 1290 > 2700 > Ready; T=0.01/0.01 16:05:41 > > I used the version of vmlink created in september 2010 > > Alain Benveniste >
