Hi, Amit Karpe <[email protected]> (Di 19 Mär 2013 04:51:50 CET): > Hi All, > I am facing new problem with my NAS filesystem with particular directory. ( > Till yesterday I was trying to improve speed of my backup.) > File system on NAS is working well as I can access other directories and > even I can copy files from NAS to there system. > > But I can't access this directory /nasbackup/full/holdingdisk/20130318133816 > If I fire "ls" command is just hand there & even I can't kill using kill > command.
If NFS is stuck and mounted as non-interruptible, you're out of luck.
> My question "Is my File system corrupt ?" How I can cross check ?
> Regular fsck I can't use I don't have access to NAS command prompt.
…
So probably via NFS, because iSCSI would give you a block device which
you could check.
> [root@borneo data]#
> Message from syslogd@borneo at Mar 18 23:02:11 ...
> kernel:------------[ cut here ]------------
> Message from syslogd@borneo at Mar 18 23:02:11 ...
> kernel:invalid opcode: 0000 [#2] SMP
I'm not a kernel programmer, but invalid opcode does not look good.
May be your local file system is corrupted, giving you corrupted
binaries.
I'd say invalid opcode may be caused by invalid binaries (just some
defective bit) or by unreliable memory. (Run memtest…)
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: 7CBF764A -
gnupg fingerprint: 9288 F17D BBF9 9625 5ABC 285C 26A9 687E 7CBF 764A -
(gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B)-
signature.asc
Description: Digital signature
