[linux-lvm] "Close failed: Bad file descriptor" messages on pvcreate

[linux-lvm] "Close failed: Bad file descriptor" messages on pvcreate

[Sreedharan_Vinod]

Hi,

When I do pvcreate, I get deluged with "pvcreate  /dev/sdf: close failed:
Bad file descriptor" messages.

I need to explicity open another session to kill the previous pvcreate
instance to get out of this situation.

On the same system, pvcreate another device succeeds.

Distro:  RHEL 4.0 GA version
version  LVM version:     2.00.31 (2004-12-12)
version  Library version: 1.00.19-ioctl (2004-07-03)
version  Driver version:  4.3.0

:~ # dd if=/dev/sdf of=/dev/null bs=1k count=2
2+0 records in
2+0 records out
:~ # dd if=/dev/sde of=/dev/null bs=1k count=2
2+0 records in
2+0 records out

# pvcreate /dev/sde
pvcreate  Physical volume "/dev/sde" successfully created

# pvcreate /dev/sdf
pvcreate  /dev/sdf: close failed: Bad file descriptor
pvcreate  /dev/sdf: close failed: Bad file descriptor
pvcreate  /dev/sdf: close failed: Bad file descriptor
pvcreate  /dev/sdf: close failed: Bad file descriptor


Same messages till I kill pvcreate explicitly.

I see that lvmdiskscan does NOT list /dev/sdf but does list /dev/sde

Note: I did a vgscan/pvscan explicitly after doing a "make install" of the
built 2.00.31 sources.

When I downgrade the lvm version (say: 2.00.15), make and make install --
everything seems to work find
and I am able to do a PV on both sde and sdf.  And I am able to see both
devices in lvmdiskscan output.

Any idea on what's happening here?

Thanks,
Vinod

[linux-lvm] "Close failed: Bad file descriptor" messages on pvcreate

[Sreedharan_Vinod]

> Hi,
> 
> When I do pvcreate, I get deluged with "pvcreate  /dev/sdf: close failed:
> Bad file descriptor" messages.
> 
> I need to explicity open another session to kill the previous pvcreate
> instance to get out of this situation.
> 
> On the same system, pvcreate another device succeeds.
> 
> Distro:  RHEL 4.0 GA version
> version  LVM version:     2.00.31 (2004-12-12)
> version  Library version: 1.00.19-ioctl (2004-07-03)
> version  Driver version:  4.3.0
> 
> :~ # dd if=/dev/sdf of=/dev/null bs=1k count=2
> 2+0 records in
> 2+0 records out
> :~ # dd if=/dev/sde of=/dev/null bs=1k count=2
> 2+0 records in
> 2+0 records out
> 
> # pvcreate /dev/sde
> pvcreate  Physical volume "/dev/sde" successfully created
> 
> # pvcreate /dev/sdf
> pvcreate  /dev/sdf: close failed: Bad file descriptor
> pvcreate  /dev/sdf: close failed: Bad file descriptor
> pvcreate  /dev/sdf: close failed: Bad file descriptor
> pvcreate  /dev/sdf: close failed: Bad file descriptor
> 
> 
> Same messages till I kill pvcreate explicitly.
> 
> I see that lvmdiskscan does NOT list /dev/sdf but does list /dev/sde
> 
> Note: I did a vgscan/pvscan explicitly after doing a "make install" of the
> built 2.00.31 sources.
> 
> When I downgrade the lvm version (say: 2.00.15), make and make install --
> everything seems to work find
> and I am able to do a PV on both sde and sdf.  And I am able to see both
> devices in lvmdiskscan output.
> 
> Any idea on what's happening here?
> 
> Thanks,
> Vinod
> 
> 
> 
> 

Re: [linux-lvm] "Close failed: Bad file descriptor" messages on pvcreate

[Alasdair G Kergon]

On Wed, May 04, 2005 at 10:49:00AM +0100, Sreedharan_Vinod@emc.com wrote:
> > When I do pvcreate, I get deluged with "pvcreate  /dev/sdf: close failed:
> > Bad file descriptor" messages.

> > On the same system, pvcreate another device succeeds.

What architecture is this?

It sounds similar to a known bug that is fixed in the RHEL4 Update 1 package.

Alasdair
-- 
agk@redhat.com

Re: [linux-lvm] "Close failed: Bad file descriptor" messages on pvcreate

[Jeffrey Johnson]

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

On 5/3/05, Sreedharan_Vinod@emc.com <Sreedharan_Vinod@emc.com> wrote:
> 
> Hi,
> 
> When I do pvcreate, I get deluged with "pvcreate /dev/sdf: close failed:
> Bad file descriptor" messages.
> 
> I need to explicity open another session to kill the previous pvcreate
> instance to get out of this situation.
> 
> On the same system, pvcreate another device succeeds.
> 

I've had the same problem with some SAN attached storage. I was able to 
workaround it by doing a vgcreate using the physical volume pvcreate failed 
on. This will obviously fail, but a subsequent pvcreate on the device will 
then work.

[-- Attachment #2: Type: text/html, Size: 982 bytes --]