Summary: Overlapping partition problem

From: Smith, Mike R. <smithmr_at_bowater.com>
Date: Mon, 23 Jun 2003 15:28:07 -0400

Sorry this summary took so long but we just found the answer. The credit goes to a Jean-Marie at HP support. The problem was that the swxcrmon process for some unknown reason appeared to have a hold on that partition. I rebooted over the weekend and I was able to do anything I wanted to with that partition when booted from the install cd. This led us to believe it was something that started when the system came up. We used fuser and lsof trying to find the culprit to no avail. The problem appears to be that it was an old partition that had been unused for a while that I attempted to recycle. If I had tried to bring it up before the swcxr process was up, who knows, it might have worked. I wonder if swcxrmon remembered it from before and was trying to monitor it somehow. Once I killed both swcxr monitor processes, the partion mounted no problem.

Thanks to Pat O' Brien for the help he tried to give me also, we exchanged many an email over this issue.

Original problem

I had a partition in use on a drive which I took out a service because I got more drives so I moved the data to the new drive. Now I would like to make use of that partition but the operating system will not let me. I first tried mounting to another directory (old one in use with new partition) but it gave me the following:

Error: an overlapping partition is open.

I used diskconfig to make it unused and tried to newfs it, same problem. Fuser and lsof show no use of this partition, I have had two people from HP (problem was escalated) verify from disklabel that none of the partitions on that drive overlap. I have used diskconfig to shrink it a little more and re-added it back and still it says there is an overlapping partition. I am running 5.1 pk 6, anyone seen anything like this before? HP asked me to shutdown and boot from the cd and then try the newfs but this is production so that will have to be done later. Any ideas what would cause this?
Received on Mon Jun 23 2003 - 19:29:29 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:44 NZDT