Dynamic volumes on WXPP SP2 make folder and file shares read only

[Guest]

I have converted the boot disk from basic partition to a simple dynamic
volume on two workstations running Windows XP Professional with all available
patches (through automatic updates). The reason for this was to enable
dynamic extensions.

Now folder and file shares served by these machines have become read only:
existing files cannot be updated or deleted. However, new files may be
created. The new files may again not be updated.

How can this problem be resolved?

I have tried to modify the LanMan Server (and workstation) parameters to no
avail. Disabling opportunistic lock parameters does not seem to make any
difference.

Could it be that dynamic volumes converted from basic partitions created by
WXPP SP1 is to blame. I have found that these volumes cannot be extended as
they were created by an older version of WXPP.

Reversing the conversion is not possible.

 

[Kerry Brown]

I have converted the boot disk from basic partition to a simple dynamic
volume on two workstations running Windows XP Professional with all
available
patches (through automatic updates). The reason for this was to enable
dynamic extensions.

Now folder and file shares served by these machines have become read only:
existing files cannot be updated or deleted. However, new files may be
created. The new files may again not be updated.

How can this problem be resolved?

Update the NTFS and Share permissions. It sounds like something may have
gone wrong in the conversion process.

I have tried to modify the LanMan Server (and workstation) parameters to
no
avail. Disabling opportunistic lock parameters does not seem to make any
difference.

Could it be that dynamic volumes converted from basic partitions created
by
WXPP SP1 is to blame. I have found that these volumes cannot be extended
as
they were created by an older version of WXPP.

Boot volumes cannot be extended. It has nothing to do with versions. It is a
limitation of dynamic volumes that is well documented.

Reversing the conversion is not possible.

Yes it is. Delete the volumes, recreate them as basic volumes, then restore
the data from your backups you created before you started this process

Kerry

 

[Guest]

Kerry,
Thanks for your response.

Update the NTFS and Share permissions. It sounds like something may have
gone wrong in the conversion process.

I have removed and recreated the permissions. I does not make any difference.
The share access rights problem is identical for both systems, although they
were done independently of each other. To me, it seems to have to do with the
conversion process to dynamic volumes.

Boot volumes cannot be extended. It has nothing to do with versions. It is a
limitation of dynamic volumes that is well documented.


Yes it is. Delete the volumes, recreate them as basic volumes, then restore
the data from your backups you created before you started this process

Well. Right.
As the share read-only problem was not noticed until some time after the
conversion, a number of email were received after the conversion. In
addition, as files were updated to the shares by creating new files with new
names and deleting the old, I need to restore backups made from the converted
dynamic volumes.
Can I restore the ASR backups to basic volumes although they were taken from
Dynamic volumes and not loosing any data? Notice, they are systems volume
backups, not only data.

 

[Guest]

Update the NTFS and Share permissions. It sounds like something may have
gone wrong in the conversion process.


Boot volumes cannot be extended. It has nothing to do with versions. It is a
limitation of dynamic volumes that is well documented.


Yes it is. Delete the volumes, recreate them as basic volumes, then restore
the data from your backups you created before you started this process

Kerry

Is there a way to resolve the access rights situation, instead of restoring
to a previous setup? To me, it seems that it *should* be possible get the
proper access, i.e. read/right to existing files. On basic partitions it is.
Creating a new file, e.g. by using the new file right click option and
deleting the file within a few seconds, does work. Provided the file is not
opened, it can be deleted. Doing a window refresh does not update the file,
thus allowing deletion. Checking properties of the file is sufficient to
prevent deletion. A locked file cannot be deleted directly from the system
holding the file, except after a reboot.

Regards,
JRB

 

[Kerry Brown]

Kerry,
Thanks for your response.


I have removed and recreated the permissions. I does not make any
difference.
The share access rights problem is identical for both systems, although
they
were done independently of each other. To me, it seems to have to do with
the
conversion process to dynamic volumes.
Well. Right.
As the share read-only problem was not noticed until some time after the
conversion, a number of email were received after the conversion. In
addition, as files were updated to the shares by creating new files with
new
names and deleting the old, I need to restore backups made from the
converted
dynamic volumes.
Can I restore the ASR backups to basic volumes although they were taken
from
Dynamic volumes and not loosing any data? Notice, they are systems volume
backups, not only data.

I was being facetious. At this point I would leave the volumes as dynamic
and fix the permissions problem. Check who owns the files, check that
Creator Owner is listed in the permissions. In the Advanced settings from
the Security tab click on the effective permissions tab and type in a user
name that should have full access. What are the results?

Kerry

 

[Guest]

Kerry,

Before converting the disks to dynamic volumes, the shares were already in
place and operating perfectly since 2002, when I first bought the machines
(HP xw4100) with WXPP. Access is controlled using ACLs. I moved the folders
with the shares from WNT systems) on DEC Alpha) where the same shares had
been in operation since 1997. (FYI: I have internals knowledge of OpenVMS and
was a security specialist and information integrity consultant for 15 years.
I also have extensive knowledge of Windows.)
The permissions are the same as before the conversion to dynamic volumes.
The permissions allow users of the Administrators and the System groups full
access.

It is NOT the permissions that make the files become read only. Not even a
user in the Administrators group can open e.g. a Word file other than read
only or save a .txt. file after it has been modified. Using Explorer to check
the properties of any file will make it non-delete-able. However, any new
file can be created.
The files become "locked by an other Person or program". It is a lock
problem, as I wrote initially. That is why I have tried to modify lanman
server locks.

When a file has become non-delete-able, it cannot even be deleted directly
on the system holding the share, be it by an Administrator or the owner of
the file.
Only after a reboot can the file be deleted, through any of tools available,
be it over the net (in the share) or directly on the dynamic volume using
Explorer or DOS delete or any other program that can delete files.
Only when a file is created and modified over the net will it become locked.
Files are shared over the local area and are accessible to specific users
only, and to Administrators and System.
Accessing the administrative shares (disk$) as an administrator show the
same looking problem. Files become looked by the process with pid 4 system!

Thanks,
JRB

 

[Kerry Brown]

As I said before, something obviously went wrong in the conversion process.
What you are experiencing is not normal with dynamic volumes. If it is not a
permissions issue then I don't know the answer. Maybe someone else will
know. It might be easier to backup the data, delete then recreate the
shares, and restore the data. As a test you could create a new share on the
volume and see if it has the same problems.

As an aside I have seen very strange behaviour when the Creator Owner
permissions get messed up. Usually this shows up when you check what the
effective permissions are.

Kerry

 

[Guest]

Kerry,

Thank you for effort.
I have removed the shares and recreated them again.
It makes no difference.
In addition, as the problem shows up also for the administrative shares, I
do not think it is the shares or their permissions that is the problem.
Rather, it is related to the network services and locking.
A lock is set when a file is opened, but never released. Thus, it is not
possible to update the file.

Obviously, something went wrong at the conversion to dynamic volume.
As the identical behaviour resulted on the other system, I suspect a bug in
the conversion process or tools (Disk Admin)...

Regards,
JRB

 

[Kerry Brown]

Kerry,

Thank you for effort.
I have removed the shares and recreated them again.
It makes no difference.
In addition, as the problem shows up also for the administrative shares, I
do not think it is the shares or their permissions that is the problem.
Rather, it is related to the network services and locking.
A lock is set when a file is opened, but never released. Thus, it is not
possible to update the file.

Obviously, something went wrong at the conversion to dynamic volume.
As the identical behaviour resulted on the other system, I suspect a bug
in
the conversion process or tools (Disk Admin)...

If it was a bug Googling for the problem would get some hits. I suspect
something in your setup but you never know. I have converted several servers
(2k and 2003) to dynamic disks but never XP. Maybe XP does something
different.

Kerry