Dell PowerVault NX3610 User Manual - Page 75

CIFS Path Share Not Found, CIFS Write To Read Only Volume, Restore the problematic path from a backup.

Get Dell PowerVault NX3610 PDF manuals and user guides View all Dell PowerVault NX3610 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 75 highlights

Workaround CIFS Path Share Not Found Description Cause Workaround CIFS Write To Read Only Volume Description Cause List the available NAS shares and verify that all shares are displayed and nothing has changed unintentionally. Verify that you can access the problematic share using a Windows client: 1. Click Run. 2. Enter the client access VIP and share name: \ \\ Client accessed a share which refers to an inexistent directory in the NAS container. • The NAS system is restored from a backup or remote replication. During restore time, the directory structure is not complete and a few directories may not exist. Communicate the status and wait for the restore process to complete. • A client with an authorization to access a higher directory in the same path deleted or altered a directory, which is mounted by another client. If multiple users are accessing the same dataset, it is recommended to apply a strict permission scheme to avoid such conflicts. List all available shares on the NAS and identify the problematic share. It must have an indication that it is not accessible. 1. Restore the problematic path from a backup. 2. Manually create the missing directories. Set permissions to control access as required. 3. Remove the share and communicate to the client. Client tries to modify a file on read-only volume. A NAS volume is set to read-only when it is the target of a replication. The most frequent reason for this event is either: • The user meant to access the target system for read purposes, but also tries to modify a file by mistake. • The user accesses the wrong system due to similarity in name/IP. • The user is accessing a NAS container, which was made a replication target without his knowledge. 75

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
Workaround
List the available NAS shares and verify that all shares are
displayed and nothing has changed unintentionally.
Verify that you can access the problematic share using a
Windows client:
1. Click
Run
.
2. Enter the client access VIP and share name:
\
\<Client_VIP>\<CIFS_share_name>
CIFS Path Share Not Found
Description
Client accessed a share which refers to an inexistent
directory in the NAS container.
Cause
•
The NAS system is restored from a backup or
remote replication. During restore time, the
directory structure is not complete and a few
directories may not exist.
Communicate the status and wait for the restore
process to complete.
•
A client with an authorization to access a higher
directory in the same path deleted or altered a
directory, which is mounted by another client.
If multiple users are accessing the same dataset,
it is recommended to apply a strict permission
scheme to avoid such conflicts.
Workaround
List all available shares on the NAS and identify the
problematic share. It must have an indication that it is not
accessible.
1. Restore the problematic path from a backup.
2. Manually create the missing directories. Set
permissions to control access as required.
3. Remove the share and communicate to the client.
CIFS Write To Read Only Volume
Description
Client tries to modify a file on read-only volume.
Cause
A NAS volume is set to read-only when it is the target of a
replication.
The most frequent reason for this event is either:
•
The user meant to access the target system for
read purposes, but also tries to modify a file by
mistake.
•
The user accesses the wrong system due to
similarity in name/IP.
•
The user is accessing a NAS container, which
was made a replication target without his
knowledge.
75