.: No such device or address

[Nik_1]

Hi,

Ok, before I go any further, this is a solaris box (don't flame me! 99% I use HPUX!) Anyway, you guys always help me out so quickly, I just wondered if anyone could help on this one... it's not exactly solaris, I guess it could apply to HP?

I have a kinda weird problem, where If I 'cd' into a directory it's ok, but when I do an 'ls' I get:

.: No such device or address

If I do a 'df -k' the directory is mounted on:

/dev/vx/dsk/datadg/oldlogs

and I can 'ls -la' that file and get:

brw------- 1 root root 157,106023 Dec 3 1999 oldlogs

Now we did replace this disk the other day, but I have other directories mounted on /dev/vx/dsk/datadg which are working ok...

thanks!
Nik

[Steve Steel]

Hi

Guess that it is marked as mounted but isnt.

Try to unmount and remount.


cd would just go to mountpoint

ls would give . (current directory )
no such device or address0

Steve Steel

[Roger Baptiste]

hi,

I guess, the directory(filesystem) is not mounted. Do a grep "directory" /etc/fstab to see it's mount source and then run the mount command using that info.

HTH
raj

[Bill McNAMARA_1]

did you reboot since replacing the disk?

It's odd that it would appear as such if the rest of the filesystem is okay. Are you certain it's all one filesystem?

What does the /etc/fstab and /etc/mnttab reveal?

Later,
Bill

[Nik_1]

Thanks for the responses!

If I try and mount it I get:

vxfs mount: Cannot open /dev/vx/dsk/datadg/oldlogs: No such device or address.

But the device file exists and looks ok? (see above)

Nik

[Bill McNAMARA_1]

The disk has possibly not been recognised at the same hardware location.. or not activated by the disk management subsystem.
It doesn't necessarily mean the device files are invalid, but that the device file to hardware liason is.

You should ask on the sun forums, I'm sure you'll get a diagnostic from there.
http://forum.sun.com

Later,
Bill

[Nik_1]

Thanks for your help everyone. I'm off to forum.sun.com

[Wodisch]

Hi Nik,

maybe you check back some day...

Since the output of your "ls -l" shows the file type to be a BLOCK DEVICE this will never work! Somehow somebody has removed the directory "oldlogs" and created (mknod) a block device instead in its place - very nasty idea :-(

"rm" that block device file, "mkdir" the oldlogs dir again, and try again, would be my advice...

HTH,
Wodisch