On Fri, 23 Nov 2007 07:36:44 +0100 Dirk Heinrichs <[EMAIL PROTECTED]> wrote:
> Am Donnerstag, 22. November 2007 schrieb ext Stroller: > > > A Google seems to suggest that "mount: No buffer space available" > > is commonly returned when the device is already mounted. > > I also found (with Google) one forum posting where it was stated that > the cause was a bad, self-burned disk in the drive. When the poster > changed the disk, the problem disapeared. > > Bye... > > Dirk Who knows? If the mounting process does a whole bunch of stuff before allocating buffer space or dying on that error, it's difficult to say what's going on ... without looking at the code. -- [EMAIL PROTECTED] mailing list
