This is a discussion on RE: [Samba] Printing Problem with Samba ' Failed to allocate a within the Samba forums, part of the Networking and Network Related category; Hi Bill, That would be fabulous (in a bad way) but it is not the case. Here is = the equivalent ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hi Bill,
That would be fabulous (in a bad way) but it is not the case. Here is = the equivalent part of dumpe2fs for /dev/sda1 (/data): Inode count: 183156736 Block count: 366286008 Reserved block count: 18314300 Free blocks: 287497221 Free inodes: 181068686 And here is for /dev/sdf1 (/): Inode count: 14057472 Block count: 28103701 Reserved block count: 1405185 Free blocks: 17311944 Free inodes: 13849218 Any other ideas would be appreciated! --Misty -----Original Message----- From: William Jojo [mailto:jojowil@hvcc.edu]=20 Sent: Tuesday, April 08, 2008 1:49 PM To: Misty Stanley-Jones Subject: Re: [Samba] Printing Problem with Samba ' Failed to allocate a = print job' This will sound stupid, I am certain, but is this an inode issue? Does = the FS type you are using auto-extend (like JFS2 on AIX) the number of = available inodes? Or fragmentation perhaps? I only ask since you clearly have enough space, but a lack of inode may = appear as no space left on device and a high level of fragmentation in = JFS (not jfs2) on AIX will throw strange errors. Cheers, Bill (PS: I know you are not running AIX. :-) :-) ) No virus found in this outgoing message. Checked by AVG.=20 Version: 7.5.519 / Virus Database: 269.22.9/1365 - Release Date: = 4/8/2008 7:30 AM =20 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba |