| 1 |
On Fri, 23 Nov 2007 07:36:44 +0100 |
| 2 |
Dirk Heinrichs <dirk.heinrichs.ext@×××.com> wrote: |
| 3 |
|
| 4 |
> Am Donnerstag, 22. November 2007 schrieb ext Stroller: |
| 5 |
> |
| 6 |
> > A Google seems to suggest that "mount: No buffer space available" |
| 7 |
> > is commonly returned when the device is already mounted. |
| 8 |
> |
| 9 |
> I also found (with Google) one forum posting where it was stated that |
| 10 |
> the cause was a bad, self-burned disk in the drive. When the poster |
| 11 |
> changed the disk, the problem disapeared. |
| 12 |
> |
| 13 |
> Bye... |
| 14 |
> |
| 15 |
> Dirk |
| 16 |
|
| 17 |
Who knows? If the mounting process does a whole bunch of stuff before |
| 18 |
allocating buffer space or dying on that error, it's difficult to say |
| 19 |
what's going on ... without looking at the code. |
| 20 |
-- |
| 21 |
gentoo-user@g.o mailing list |
Archives