I'm currently using a Debian Wheezy server with a iSCSI block target "lun0". This target is mounted on my Windows 2008 R2 machine and formated using NTFS. The device is mounted as "D:\DATA" and shared as "\DATA". Other machines are connecting to this share - not directly to the iSCSI target (because I know that this isn't supported using NTFS ;-) )

Sometimes I get "NTFS attribute corrupt" messages while running chkdsk on this mounted iSCSI target. Like "Attribute (128,"") from data segment "XXXXX" is corrupted" (translated, I don't know the correct english description ...)

Does anyone know how to fix this problem?

Thanks for your help! :)

  • Is the lun also mounted on the Debian system ? – Stephane May 6 '14 at 8:40
  • Nope. Just on the windows machine. – Screeny May 6 '14 at 8:43
  • In my experience, NTFS (in recent versions anyway), in itself, is VERY resilient: corruption is usually the result of storage-level errors. In your case, you're using iSCSI which implies a ddep network stack. Now, the guideline in implementing iSCSI storage is to separate storage network and general purpose network because general purpose networking is resilient to things like packet loss and changes in latency, two things that iSCSI do not deal with very well (if at all). Did you separate these networks ? – Stephane May 6 '14 at 9:06
  • No, I dind't seperated the networks - maybe this is the problem. I will try to seperate these networks, thanks so far! – Screeny May 6 '14 at 9:48
  • Did I write a long and complex comment just to ask "is your iSCSI network isolated" ? Looks like I did, yes... Sorry – Stephane May 6 '14 at 9:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.