Sorry for the delay in getting back to you; I've been on travel this
past week, didn't have much time to keep completely up on e-mail.
On Mon, May 14, 2007 at 04:40:26PM -0500, Shapor Naghibzadeh wrote:
> My point with the USB example was that it keeps their labels around in a
> world-readable cac
On Thu, May 10, 2007 at 02:44:48AM -0400, Theodore Tso wrote:
> put it. The device names of USB storage devices end up getting
> reused, so in practice what is in blkid.tab is merely the last storage
> device that was plugged in, not every single one going back forever.
My point with the USB exam
On Wed, May 09, 2007 at 11:45:32PM -0500, Shapor Naghibzadeh wrote:
> This issue came up while doing development work on a snapshot and remote
> replication project called zumastor (http://zumastor.googlepages.com). Every
> snapshot is assigned a new snapshot id, and over time the blkid.tab gets
>
On Wed, May 09, 2007 at 05:30:05PM -0700, Andreas Dilger wrote:
> Is there something unusual about your system or startup scripts that is
> causing so many entries in /etc/blkid.tab file?
This issue came up while doing development work on a snapshot and remote
replication project called zumastor (
On May 09, 2007 17:06 -0500, Shapor Naghibzadeh wrote:
> There is a serious performance degradation with the mount command after
> mounting many unique devices when compiled with libblkid support. A simple
> "mount" command to display the list of mounted filesystem can take minutes to
> run. Thi
There is a serious performance degradation with the mount command after
mounting many unique devices when compiled with libblkid support. A simple
"mount" command to display the list of mounted filesystem can take minutes to
run. This is due to a call to libblkid's blkid_get_cache and a
relative
