This is a discussion on ufsdump error within the Sun Solaris Administration forums, part of the Solaris Operating System category; --> When trying to use "ufsdump 0f /dev/rmt/0cn /usr" I get the following error.... DUMP: Unexpected condition detected: /dev/rmt/0cn must ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| When trying to use "ufsdump 0f /dev/rmt/0cn /usr" I get the following error.... DUMP: Unexpected condition detected: /dev/rmt/0cn must have exactly one link. DUMP: Needs Attention: cannot open 'eagle:/dev/rmt/0cn' The drive is OK - I can dump to /dev/rmt/0c, tar also works to /dev/ rmt/0cn. boot -r did not fix it. Sun external scsi tape (Exabyte 8900 Mamoth) on Solaris 9 |
| ||||
| f.nardis@gmail.com wrote: > When trying to use "ufsdump 0f /dev/rmt/0cn /usr" I get the following > error.... > > DUMP: Unexpected condition detected: /dev/rmt/0cn must have exactly > one link. Never seen that before, but it's explained in the source code: http://cvs.opensolaris.org/source/xr...ump/dumpmain.c 1482 * Bad link count implies someone's linked our 1483 * target to something else, which we probably 1484 * shouldn't step on. 1485 */ 1486 if (post_lstat.st_nlink != 1) { 1487 errtext = gettext( 1488 "Unexpected condition detected: %s must have exactly one link\n"), 1489 msg(errtext, filename); 1490 syslog(LOG_WARNING, errtext, filename); 1491 (void) close(fd); 1492 errno = EPERM; 1493 return (-1); 1494 } So check if anyone made a hard link to the device, check the link count with ls -li, ls -liL and find the other links that have the same inode. |