All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] "Close failed: Bad file descriptor" messages on pvcreate
@ 2005-05-04  4:15 Sreedharan_Vinod
  2005-05-11 17:23 ` Jeffrey Johnson
  0 siblings, 1 reply; 4+ messages in thread
From: Sreedharan_Vinod @ 2005-05-04  4:15 UTC (permalink / raw)
  To: linux-lvm

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

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [linux-lvm] "Close failed: Bad file descriptor" messages on pvcreate
@ 2005-05-04  9:49 Sreedharan_Vinod
  2005-05-04 12:28 ` Alasdair G Kergon
  0 siblings, 1 reply; 4+ messages in thread
From: Sreedharan_Vinod @ 2005-05-04  9:49 UTC (permalink / raw)
  To: linux-lvm



> 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
> 
> 
> 
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-05-11 17:23 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-04  4:15 [linux-lvm] "Close failed: Bad file descriptor" messages on pvcreate Sreedharan_Vinod
2005-05-11 17:23 ` Jeffrey Johnson
  -- strict thread matches above, loose matches on Subject: below --
2005-05-04  9:49 Sreedharan_Vinod
2005-05-04 12:28 ` Alasdair G Kergon

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.