All of lore.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: Neil Brown <neilb@suse.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, NFS@lists.sourceforge.net
Subject: Re: uuid/blkid performance problem with large number of mounts - was: Re:  stale nfs file handle with exported loopback mounts
Date: Thu, 15 Nov 2007 08:54:24 +0100	[thread overview]
Message-ID: <2086127644@web.de> (raw)

> No one (that I know of) looks at the issue tracker on sourceforge at all.
ah -ok, sorry - i didn`t know. since there were recent  entries  from octob=
er, i thought it was an official way to report bugs.

> I have it on my personal "list of things to look at one day", so maybe
> it won't get forgotten.
thanks. =

if i`m allowed to add a comment:
a public bugtracker has one advantage: others can easily see that this or a=
nother bug exists and maybe they can provide (parts of) a solution or don`t=
 need to ask for such.
i`m just too used to open source having open bugtrackers, so i thought it w=
as the right way to go.  =


if bugs not being tracked there and and you explicitly discourage using it =
- what about disabling the bugtracker entirely ?

roland



> -----Urspr=FCngliche Nachricht-----
> Von: Neil Brown <neilb@suse.de>
> Gesendet: 15.11.07 06:27:07
> An: devzero@web.de
> CC: "J. Bruce Fields" <bfields@fieldses.org>, NFS@lists.sourceforge.net
> Betreff: Re: [NFS] uuid/blkid performance problem with large number of mo=
unts - was: Re:  stale nfs file handle with exported loopback mounts


> =

> On Tuesday November 13, devzero@web.de wrote:
> > since i posted 2 problems in one mail - and one problem is solved now, =
for the second problem i have opened a ticket at =

> > =

> > http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1831403&gr=
oup_id=3D14&atid=3D100014  =

> > ( uuid/blkid performance problem with large number of mounts )
> > =

> > so this won`t get lost.
> =

> Unfortuantely that is a bit like saying "I've placed in the nice round
> filling cabinet so it won't get lost", not realising that the nice
> round filing cabinet is actually a garbage be.
> =

> No one (that I know of) looks at the issue tracker on sourceforge at
> all.
> =

> I have it on my personal "list of things to look at one day", so maybe
> it won't get forgotten.
> =

> thanks,
> NeilBrown
> =



_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=3D100071&distributionid=3D000000000066


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-11-15  7:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15  7:54 devzero [this message]
2007-11-15 16:53 ` uuid/blkid performance problem with large number of mounts - was: Re: stale nfs file handle with exported loopback mounts J. Bruce Fields
  -- strict thread matches above, loose matches on Subject: below --
2007-11-15 20:07 devzero
2007-11-15 20:12 ` Trond Myklebust
2007-11-16  1:10   ` Neil Brown
2007-11-16  1:57     ` Trond Myklebust
2007-11-16  1:58       ` Trond Myklebust
2007-11-16  3:18       ` J. Bruce Fields
2007-11-16  3:24         ` Neil Brown
2007-11-13 22:44 devzero
2007-11-15  5:26 ` Neil Brown
2007-11-15 17:23   ` Trond Myklebust

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2086127644@web.de \
    --to=devzero@web.de \
    --cc=NFS@lists.sourceforge.net \
    --cc=bfields@fieldses.org \
    --cc=neilb@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.