| 1 |
Joerg Schilling wrote: |
| 2 |
> Dale<rdalek1967@×××××.com> wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> Well whether k3b knows it or not, there is 320Gbs of space left. I did |
| 6 |
>> some more testing and the drive really doesn't do anything now. Even |
| 7 |
>> hdparm can't read all the info so I ordered a drive about 12 hours ago. |
| 8 |
>> I have had this brand before so maybe it will be OK. |
| 9 |
>> |
| 10 |
> Well, since a while, Linux did follow Solaris and offers tmpfs on /tmp. |
| 11 |
> tmpfs usually has the size of the RAM + sizeof Swap - something. |
| 12 |
> |
| 13 |
> Many programs still don't know about this limitation and try to put |
| 14 |
> temporary files of any size into /tmp. Try to reconfigure k3b.... |
| 15 |
> |
| 16 |
> Jörg |
| 17 |
> |
| 18 |
> |
| 19 |
|
| 20 |
This turned into a book. The bottom few paragraphs are the most |
| 21 |
important parts. It ends up working tho, just weirdly. Is that a |
| 22 |
word? o_O |
| 23 |
|
| 24 |
Well, I got my shiney new DVD drive. It still doesn't burn a thing. I |
| 25 |
still get this which looks like the same error to me: |
| 26 |
|
| 27 |
Burned media |
| 28 |
----------------------- |
| 29 |
DVD+RW |
| 30 |
|
| 31 |
Devices |
| 32 |
----------------------- |
| 33 |
HL-DT-ST DVD-RAM GH22NP20 2.00 (/dev/hdd, CD-R, CD-RW, CD-ROM, DVD-ROM, |
| 34 |
DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R |
| 35 |
Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, |
| 36 |
DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R |
| 37 |
Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, |
| 38 |
RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] |
| 39 |
|
| 40 |
K3b::IsoImager |
| 41 |
----------------------- |
| 42 |
mkisofs print size result: 2295193 (4700555264 bytes) |
| 43 |
|
| 44 |
System |
| 45 |
----------------------- |
| 46 |
K3b Version: 1.91.0 |
| 47 |
KDE Version: 4.4.2 (KDE 4.4.2) |
| 48 |
QT Version: 4.6.2 |
| 49 |
Kernel: 2.6.30-gentoo-r8 |
| 50 |
|
| 51 |
Used versions |
| 52 |
----------------------- |
| 53 |
mkisofs: 2.1.1a77 |
| 54 |
growisofs: 7.1 |
| 55 |
|
| 56 |
growisofs command: |
| 57 |
----------------------- |
| 58 |
/usr/bin/growisofs -Z /dev/hdd=/dev/fd/0 -use-the-force-luke=notray |
| 59 |
-use-the-force-luke=tty -use-the-force-luke=4gms |
| 60 |
-use-the-force-luke=tracksize:2295193 -speed=4 |
| 61 |
-use-the-force-luke=bufsize:32m |
| 62 |
|
| 63 |
mkisofs |
| 64 |
----------------------- |
| 65 |
/usr/bin/mkisofs: Warning: Cannot add inode hints with -no-cache-inodes. |
| 66 |
2295193 |
| 67 |
/usr/bin/mkisofs: Warning: Cannot add inode hints with -no-cache-inodes. |
| 68 |
|
| 69 |
mkisofs calculate size command: |
| 70 |
----------------------- |
| 71 |
/usr/bin/mkisofs -gui -graft-points -print-size -quiet -volid |
| 72 |
Home_2010.04.10-12.06.22_1 -volset -appid K3B THE CD KREATOR (C) |
| 73 |
1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid |
| 74 |
LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-dale/k3bQt5497.tmp |
| 75 |
-rational-rock -hide-list /tmp/kde-dale/k3bfl5497.tmp -joliet |
| 76 |
-joliet-long -hide-joliet-list /tmp/kde-dale/k3bNZ5497.tmp |
| 77 |
-no-cache-inodes -udf -full-iso9660-filenames -iso-level 3 -path-list |
| 78 |
/tmp/kde-dale/k3bqP5497.tmp |
| 79 |
|
| 80 |
mkisofs command: |
| 81 |
----------------------- |
| 82 |
/usr/bin/mkisofs -gui -graft-points -volid Home_2010.04.10-12.06.22_1 |
| 83 |
-volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND |
| 84 |
MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 |
| 85 |
-volset-seqno 1 -sort /tmp/kde-dale/k3bCQ5497.tmp -rational-rock |
| 86 |
-hide-list /tmp/kde-dale/k3bda5497.tmp -joliet -joliet-long |
| 87 |
-hide-joliet-list /tmp/kde-dale/k3bFs5497.tmp -no-cache-inodes -udf |
| 88 |
-full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-dale/k3byg5497.tmp |
| 89 |
|
| 90 |
|
| 91 |
The regular window that is open during the burning process still gives |
| 92 |
the "no space left on device" error. |
| 93 |
|
| 94 |
For the record. This is the results of df: |
| 95 |
|
| 96 |
root@smoker ~ # df |
| 97 |
Filesystem 1K-blocks Used Available Use% Mounted on |
| 98 |
/dev/hda6 9767184 1135488 8631696 12% / |
| 99 |
udev 10240 204 10036 2% /dev |
| 100 |
/dev/hda1 186663 34740 142286 20% /boot |
| 101 |
/dev/hda7 9767184 5070976 4696208 52% /home |
| 102 |
/dev/hda9 7815308 4810880 3004428 62% /usr |
| 103 |
/dev/hdb5 19228276 8309876 9941652 46% /usr/portage |
| 104 |
/dev/hda10 3718856 1301408 2417448 35% /var |
| 105 |
/dev/hdb1 9614116 183056 8942688 3% /var/tmp/portage |
| 106 |
/dev/sda1 732549604 335804932 396744672 46% /data |
| 107 |
none 1037236 0 1037236 0% /dev/shm |
| 108 |
root@smoker ~ # |
| 109 |
|
| 110 |
|
| 111 |
I configured k3b to use /data/tmp/ for temp files. It has well over |
| 112 |
300Gbs of free space. I don't know what is out of space but it ain't my |
| 113 |
hard drives. |
| 114 |
|
| 115 |
So, I stuck in a brand new, never been touched, DVD. It tried to do the |
| 116 |
formatting part but it failed. It gave the option to load anyway so I |
| 117 |
told it to load and try burning. After all that, I get the same error |
| 118 |
listed above. It still says no space left. |
| 119 |
|
| 120 |
All the previous was with app-cdr/cdrtools-2.01.01_alpha77. I then |
| 121 |
installed cdrtools-2.01.01_alpha75, logged out of KDE for good measure |
| 122 |
and tried again with the same error. |
| 123 |
|
| 124 |
I then backed up a version of k3b. Same thing. No change at all. Now |
| 125 |
I am confused so I am going fishing for a while. Now that I'm back, no |
| 126 |
fish just attacked by the skeeters, I decided to try something else. I |
| 127 |
found a older backup file that was about a little smaller than 2Gbs. It |
| 128 |
burned that just fine. No problem with it at all. It will also burn a |
| 129 |
little tiny file, few Mbs or so, just fine. So, I went back to Kbackup |
| 130 |
and created a new backup file. Instead of it doing the regular "preset" |
| 131 |
4.7Gb file size, I made it a little smaller. I made it a little over |
| 132 |
4Gbs which is actually about 3.9Gbs or so. It made a few slices and it |
| 133 |
is backing them up just fine. |
| 134 |
|
| 135 |
After this, I went back and created some new backups with the preset |
| 136 |
4.7Gb DVD setting that Kbackup uses. It appears to be working now. |
| 137 |
Also, keep in mind that this was not the backups that failed last time. |
| 138 |
This is a different set of backups. |
| 139 |
|
| 140 |
So, what the heck is up with all this? Is it that Kbackup made a slice |
| 141 |
that was maybe just a wee bit to big, twice? It was a tarball so |
| 142 |
wouldn't it burn it even if it was corrupt or something? |
| 143 |
|
| 144 |
I'm going to try putting the old DVD drive in tomorrow maybe tonight and |
| 145 |
see if it works then. The new one has a black face plate and my case is |
| 146 |
beige. It sort of looks like I gave it a black eye or something. LOL |
| 147 |
If the old drive works, this is plenty weird. Oh well, I have a new DVD |
| 148 |
drive when I start to build a new rig. |
| 149 |
|
| 150 |
Sorry this was so long. I was writing as I was doing things. |
| 151 |
|
| 152 |
Dale |
| 153 |
|
| 154 |
:-) :-) |
Archives