![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to messages.doc CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [GPL Stacker compression] / dmsdos / doc|
Return to messages.doc CVS log | Up to [GPL Stacker compression] / dmsdos / doc |
1.1 root 1: dmsdos driver: kernel messages in alphabetical order.
2:
3: *** Some messages need a better explanation. Under construction :) ***
4:
5: Classes: I: Information.
6: E: Error in filesystem, check it under dos (incl. the surface test).
7: O: Other problem, not a filesystem error.
8: B: Bug, please send a bug report.
9: P: Panic message. Extremely severe filesystem, hardware or dmsdos
10: error. The process that actually called dmsdos when the problem
11: occured has been "frozen" in order to prevent data corruption.
12: Though your system continues to run, you should reboot immediately
13: and check the compressed filesystems. You may have to press the
14: reset button in order to reboot.
15: ?: Unknown. (Look at the source code.)
16:
17: ------------------------------------------------------------------------------
18:
19: DMSDOS: adapting free sectors count
20: I: Stacker sector count is corrected.
21:
22: DMSDOS: BB_ClustCnt=0x%x impossible (FAT32?)
23: E/O?: The filesystem is in an unsupported format, damaged or otherwise
24: strange. Dmsdos refuses to mount it. Please verify whether it is FAT32
25: under Dos/Win95. Currently compressed FAT32 is not supported.
26: (Compressed FAT32 has never been reported to exist so far.)
27:
28: DMSDOS: bitfat cache:
29: I: Debug message. Ignore.
30:
31: DMSDOS: BITFAT mismatches MDFAT, repairing...
32: DMSDOS: BITFAT mismatches MDFAT (sector %d is %d and should be %d)
33: DMSDOS: BITFAT mismatches MDFAT (sector %d)
34: E: There's an error in the allocation table (BITFAT) of your compressed
35: partition - next time you boot dos you should check it. WARNING:
36: Writing to an errorneous filesystem may cause further damage.
37: Optionally (with mount option bitfaterrs=repair)
38: the driver tries to repair the problem by recalculating the BITFAT.
39:
40: DMSDOS: bmap called, unsupported!
41: B: Shouldn't happen.
42:
43: DMSDOS: cannot write dirty cluster %d on dev 0x%x, trying again later
44: E/O: Very likely the filesystem is full. There should be another message
45: describing more details. The driver keeps the cluster in memory. This
46: is a very critical condition as you may lose the data in that cluster.
47: The driver usually tries 5 times to write the data again before
48: throwing them away and setting the filesystem to read-only mode. If
49: the filesystem is really full you still have a chance to free up some
50: space now.
51:
52: DMSDOS: ccache contents:
53: DMSDOS: ccache statistics:
54: I: Debug messages. Ignore.
55:
56: DMSDOS: ch_dirty(_locked): READ-ONLY filesystem
57: O: When the filesystem suddenly is set read-only (e.g. because of a
58: problem) some kernel functions seem not to obey the RO flag. In this
59: case, the dmsdos driver itself rejects the command in order to
60: avoid trashing the filesystem.
61:
62: DMSDOS: ch_read: no memory!
63: O: System memory is even too low for read access. See below for hints
64: about 'no memory' messages.
65:
66: DMSDOS: ch_read: read_cluster failed
67: E: The cluster could not be read from disk. There should be another
68: message describing more details.
69:
70: DMSDOS: check_free_sectors: wrong count %d corrected to %d
71: B: Looks like a minor bug. As the message tells, the problem is corrected.
72:
73: DMSDOS: clear_list_dev: Uhh, sb==NULL ...
74: B: Shouldn't happen.
75:
76: DMSDOS: cluster %d read error
77: E: There should be another message describing the error more exactly.
78:
79: DMSDOS: compression method not recognized.
80: E: Check filesystem. May also be caused by running incompatible/unsupported
81: or not yet fully supported compression software under dos. In detail, the
82: driver found a compressed cluster but didn't recognize the compression
83: header. This may even be suspicious to be a dmsdos bug.
84:
85: DMSDOS: could not find MDR signature or found more than one, mdrc=%d (ignored)
86: I: Debug message. It may indicate a problem with the CVF, but as this
87: signature is almost completely unimportant, you can most likely ignore
88: it.
89:
90: DMSDOS: could not guess compression method for CVF
91: I: There's no compressed file in your compressed filesystem that dmsdos
92: could analyse to determine the compression method. To avoid problems,
93: dmsdos has disabled compression when writing to this CVF. Specify a
94: compression method explicitely when mounting (comp=xxx option) or write
95: something (more than 1KB) to the compressed partition under dos.
96:
97: DMSDOS: counted free sectors=%d
98: I: The message tells how many free sectors have been counted in the CVF.
99:
100: DMSDOS: CVF almost full or highly fragmented at MDFAT level.
101: I: The driver warns that further write access might become dangerous.
102:
103: This indicates a really bad situation. The algorithm to find free space
104: in a CVF performs three trials to find an appropriate hole for new data.
105: All of them use different priorities to avoid MDFAT level fragmentation.
106: But this time it did not succeed until its last trial. That means
107: additional MDFAT level fragmentation cannot be avoided any longer and the
108: more write access you perform the more likely the last trial is to fail.
109:
110: Watch the free space on the compressed partition. If there seems to be
111: enough, try to defragment the partition as described in chapter
112: 'defragment procedures' in file dmsdos.doc.
113:
114: This message has KERN_EMERG priority to ensure you can see it on the
115: screen.
116:
117: DMSDOS: CVF end padding %d sectors.
118: I: Size of STACVOL is stored in its header. If real file is
119: longer than this information, user is informed about that
120: unused sectors. It can happens when you copy stacvol
121: to other host drive.
122:
123: DMSDOS CVF-FAT extension version %d.%d.%d
124: I: Tells version number and compile-time options when loading dmsdos.
125: The term 'read-only' means that you are using a read-only dmsdos
126: version (write access has been turned off during dmsdos configuration).
127: It does *not* tell that the filesystem is mounted read-only or
128: read-write.
129:
130: DMSDOS: CVF full.
131: DMSDOS: CVF full (cannot even allocate fragmented space)
132: DMSDOS: CVF full or too fragmented at MDFAT level.
133: O/E: The message tells it all. The last write access may have failed and
134: data may have been lost. As you cannot tell how well the data will
135: compress it is dangerous to fill a CVF up to the last byte. There might
136: even be some errors in the filesystem now (but that's very unlikely).
137:
138: These messages have KERN_EMERG priority. They indicate that something
139: dangerous has happened. The next time you boot dos you'd better check
140: the filesystem. And, of course, free up some space.
141:
142: DMSDOS: CVF has bitfat mismatches, ignored.
143: DMSDOS: CVF has bitfat mismatches, setting to read-only.
144: DMSDOS: CVF has serious errors or compatibility problems, setting to read-only.
145: I: The driver has detected an error in the filesystem and has either
146: ignored the error or set the filesystem to read-only mode. There should
147: be another message describing the error. In rare cases, the error may
148: be caused by compatibility problems.
149:
150: DMSDOS: CVF has FAT32 signature, not mounted. Please report this.
151: O: Compressed FAT32 is unsupported. I've never seen it, but I may start
152: to write support for it if someone reports that a strange M$ product
153: really creates compressed FAT32 filesystems. I don't believe so.
154:
155: DMSDOS: CVF is in doublespace format (version 1).
156: DMSDOS: CVF is in drivespace 3 format.
157: DMSDOS: CVF is in drivespace format (version 2).
158: DMSDOS: CVF is in stacker 3 format.
159: DMSDOS: CVF is in stacker 4 format.
160: I: The driver reports what it has detected.
161:
162: DMSDOS: CVF is in unknown (new?) format, please report.
163: I: The driver didn't recognize the CVF format after verifying that it is
164: indeed a CVF. Watch for further messages. You'd better not write to
165: the partition :)
166:
167: DMSDOS: CVF is shorter about %d sectors. Mounting READ ONLY.
168: E: Error in stacker filesystem. Check under dos.
169: Real length of STACVOL is smaller, than that stored in stacvol
170: header. Stacvol is probably corrupted.
171:
172: DMSDOS: CVF on device 0x%x unmounted.
173: I: The message tells it all.
174:
175: DMSDOS: CVF set to read-only.
176: I: The message tells it all.
177:
178: DMSDOS: daemon is lying about its pid
179: O/B: Either someone is trying to compromise system security by misusing
180: dmsdos ioctls (without success) or the external daemon has a bug.
181:
182: DMSDOS: daemon_write_cluster: ch==NULL
183: B: Shouldn't happen.
184:
185: DMSDOS: Data are not SQ compressed
186: E: Error in drivespace 3 filesystem (invalid data?), check under Win95.
187:
188: DMSDOS: dataend corrected due to MDR signature old=%d new=%d
189: I: Due to a problem with the loopback block device - it only gives size
190: information in units of 1K blocks and not in 512 byte sectors - dmsdos
191: cannot determine the exact end of the CVF. So, it tries to guess where
192: the real end of the compressed partition is. This guess is verified by
193: searching the MDR signature, which is typically located in the last
194: sector of the CVF. If the driver has guessed the wrong end, this is
195: automatically corrected and this message is logged. In theory, maximum
196: error can be 1 sector.
197:
198: DMSDOS: dbl_bitfat_value: version not found?? cannot happen
199: DMSDOS: dbl_mdfat_value: unknown version?? This is a bug.
200: B: Shouldn't happen.
201:
202: DMSDOS: dbl_replace_existing_cluster: checking old fraglist: first fragment wrong in cluster %d
203: E: Filesystem error in drivespace 3 volume. Check under Win95.
204:
205: DMSDOS: dbl_replace_existing_cluster: This is a bug - reboot and check filesystem
206: B: Uhh. Cut'n'paste your logfile and mail it to me. This is a serious bug.
207:
208: DMSDOS: dblspace_fat_access: READ-ONLY filesystem
209: O: When the filesystem suddenly is set read-only (e.g. because of a
210: problem) some kernel functions seem not to obey the RO flag. In this
211: case, the dmsdos driver itself rejects the command in order to
212: avoid trashing the filesystem. There's notably a problem with the
213: FAT driver, which seems to poke around in the FAT randomly after having
214: just set the filesystem to read-only mode by a filesystem panic (argh).
215: The reason is unknown (well, it doesn't seem to be really in the FAT
216: driver). To be safe, dmsdos just doesn't allow something to change the
217: FAT in that case.
218:
219: DMSDOS: dblspace_mark_buffer_dirty: READ-ONLY filesystem
220: O: When the filesystem suddenly is set read-only (e.g. because of a
221: problem) some kernel functions seem not to obey the RO flag. In this
222: case, the dmsdos driver itself rejects the command in order to
223: avoid trashing the filesystem.
224:
225: DMSDOS: decompression of cluster %d in CVF failed.
226: E/B: There's an error in the compressed data (there should be another
227: message describing what exactly failed). The next time you boot dos you
228: should check it (including the surface test since only this test finds
229: compression errors). If it is okay under dos/win95 but still fails
230: under dmsdos, *please* send a bug report (best with raw cluster data
231: extracted by using duitl).
232:
233: DMSDOS: dec_sq: submethod not tested - raw read
234: ?: Maybe a drivespace 3 problem. Check under Win95.
235:
236: DMSDOS: delete_cache_cluster: get_ch returned NULL
237: ?: Shouldn't happen. This message means that the cluster couldn't be
238: locked during deletion. So it's deleted without locking. So what.
239:
240: DMSDOS: Deleted clusters found, removing...
241: I: Cleaning up stacker filesystem.
242:
243: DMSDOS: dfat cache:
244: I: Debug message. Ignore.
245:
246: DMSDOS: dirty cluster %d on dev 0x%x removed, data are lost
247: O/E: The driver is giving up that cluster. Writing has failed more than
248: 5 times. YOU HAVE BEEN WARNED 5 TIMES! In order to prevent a system
249: lockup caused by endless loops the driver has thrown the data away.
250: THE DATA ARE DEFINITIVELY LOST NOW. Very likely the filesystem is
251: damaged now and a part of a directory is also lost.
252: The driver sets the filesystem to read-only mode (printing it in the
253: next message). This is a really bad situation. You'd better boot Dos
254: and have the CVF maintainance software repair what can be repared.
255: If the CVF repair tool permits it, save all lost clusters - they are
256: likely to contain some of the lost files.
257:
258: DMSDOS: Dirty virtual sector cannot be written - FILESYSTEM DAMAGE POSSIBLE! Trying to delay write.
259: O: THE FILESYSTEM IS FULL! It's even so full that some clusters cannot
260: be written back to the disk (they're kept in memory instead). Free up
261: some space IMMEDIATELY! Otherwise your filesystem will be destroyed
262: on unmount. After some warnings (the number depends on your cache size)
263: the driver will give up and stop the system with a panic.
264:
265: DMSDOS: dos max_cluster=%d too large, cutting to %d.
266: E?:Seems to be a filesystem error. Verify that dmsdos recognized the FAT
267: bit size correctly. If it hasn't, this is a bug.
268:
269: DMSDOS: error in DS-0-x compressed data.
270: E: There's an error in the filesystem. The next time you boot dos you
271: should check it (including the surface test).
272:
273: DMSDOS: error in JM-0-x compressed data.
274: E: There's an error in the filesystem. The next time you boot dos you
275: should check it (including the surface test).
276:
277: DMSDOS: Error while reading an mmap file %d <> %d
278: E: There should be another message describing the error more exactly.
279:
280: DMSDOS: evaluate_option: loglevel set to 0x%lx.
281: DMSDOS: evaluate_option: speedup set to 0x%lx.
282: I: The messages tell it all.
283:
284: DMSDOS: exit_daemon: counter<0 ???
285: B: Shouldn't happen.
286:
287: DMSDOS: FAT bit size not recognized, guessed %d bit
288: I: The driver did not find a valid FAT size entry in the CVF super block
289: and the emulated boot block, so it guessed the FAT size according to the
290: CVF size. This may indicate a minor filesystem error or incompatibility.
291:
292: Warning: There's a small chance to guess the wrong FAT bit size, so be
293: careful.
294:
295: Note: This message may appear on all stacker filesystems since they
296: don't seem to have a FATxx signature in the bootblock.
297:
298: DMSDOS: FAT crosslink or loop in CVF detected (cluster %d), giving up.
299: E: There's a FAT level error in your compressed filesystem. This is
300: a serious error you should immediately repair by running dos scandisk.
301:
302: Note: Verify with dutil that dmsdos has recognized the right FAT
303: bit size. If it hasn't, this is a bug.
304:
305: DMSDOS: FAT size does not match cluster count. Mounting READ ONLY.
306: E: Error in stacker filesystem.
307:
308: DMSDOS: file_mmap_nopage: no memory!
309: O: Shouldn't happen.
310:
311: DMSDOS: file_read: inode = NULL, rejected.
312: DMSDOS: file_read: mode = %07o, rejected.
313: B: Maybe a bug in the FAT driver or the rest of the kernel.
314:
315: DMSDOS: file_readx: FAT mismatches file size for ino=%ld
316: E/B: FAT error or bug.
317:
318: DMSDOS: filesystem on dev 0x%x probably damaged, set to READ-ONLY mode
319: E: The message tells it all. You'd better boot Dos and have your CVF
320: maintainance software repair the CVF.
321:
322: DMSDOS: file_write: READ-ONLY filesystem
323: O: When the filesystem suddenly is set read-only (e.g. because of a
324: problem) some kernel functions seem not to obey the RO flag. In this
325: case, the dmsdos driver itself rejects the command in order to
326: avoid trashing the filesystem.
327:
328: DMSDOS: find_free_bitfat: free sectors=%d, cannot believe this. Counting...
329: B: Something is wrong with the free sector count. The driver tries to
330: correct this by counting the free sectors again. This is a minor bug.
331:
332: DMSDOS: find_free_bitfat returned sector %d size %d but they are not all free!
333: B: Cannot happen. (Uh, oh... happened in dmsdos <= 0.6.3. Don't use them.)
334:
335: DMSDOS: fraglist!=mde cluster %d sector %d!=%ld or count %d!=%d
336: E: Error in drivespace 3 filesystem. Check under Win95.
337:
338: DMSDOS: free_ccache_dev: oh oh, freeing busy cluster...
339: B: Bug in cluster cache code. Expect a crash or hang soon. Please report.
340:
341: DMSDOS: free_cluster_sectors: error in fragmentation list in cluster %d
342: DMSDOS: free_cluster_sectors: first fragment wrong in cluster %d
343: DMSDOS: free_cluster_sectors: fragmentation list unreadable in cluster %d
344: E: Error in drivespace 3 filesystem. Check under Win95.
345:
346: DMSDOS: free sectors=%d
347: I: The number of free sectors is displayed.
348:
349: DMSDOS: free sector finding statistics:
350: I: Debug message, ignore.
351:
352: DMSDOS: get_ch: actual looks modified ARGHHH, retrying
353: DMSDOS: get_ch: free looks modified ARGHHH, retrying
354: I: Debug message. Ignore. (This messages may be important to verify that
355: new SMP safe cluster locking works correctly.)
356:
357: DMSDOS: get_ch: free->c_count!=0
358: B: Shouldn't happen. Indicates a bug (probably leak) in cluster caching
359: code.
360:
361: DMSDOS: get_ch: max_retries reached, breaking loop. This may be a bug.
362: B?: Shouldn't happen. Indicates that the driver broke an endless loop
363: to prevent a complete system hang. If you haven't run horribly out
364: of memory and you aren't loading the system to death this is an
365: extremely unlikely situation. Very suspicious to be a bug.
366:
367: DMSDOS: get_ch: oldest->c_count!=0
368: B: Shouldn't happen. Indicates a bug (probably leak) in cluster caching
369: code.
370:
371: DMSDOS: get_cluster failed (FAT problem ?)
372: O/E: The FAT driver returned an error. Maybe a problem with the FAT.
373:
374: DMSDOS: giving up after %d errors. There may be more errors.
375: I/E: The filesystem check tries to continue after the first error was
376: detected, but it definitely stops after 20 errors in order to prevent
377: your syslog from becoming larger than the errorneous filesystem.....
378:
379: DMSDOS: illegal dfat access (cluster=%d max_cluster2=%d)
380: ?: Bug or filesystem error.
381:
382: DMSDOS: illegal fragcount in cluster %d
383: E: Error in drivespace 3 filesystem. Check it under Win95.
384:
385: DMSDOS: illegal mdfat access (cluster=%d max_cluster2=%d)
386: ?: Bug or filesystem error.
387:
388: DMSDOS: illegal virtual sector %d, can't map to real sector
389: B: Problem with virtual sector mapping.
390:
391: DMSDOS: Inconsistent first data sector number. Mounting READ ONLY.
392: DMSDOS: Inconsistent sector length
393: E: Error in stacker filesystem.
394:
395: DMSDOS: init_daemon: daemon already present
396: I: Debug message, ignore.
397:
398: DMSDOS: Interesting MDFAT non-lin subalocation (cluster %d)
399: I: Will be disabled, because it is normal for stacker 4.
400:
401: DMSDOS: ioctl: D_READ: no memory!
402: O: Lack of system memory. Can be ignored. (*)[see below]
403:
404: DMSDOS: ioctl: D_READ: read_cluster failed!
405: E: Seems to be an error in your filesystem (the dmsdos daemon tried to
406: read some data but read access failed). There should be at least one
407: preceeding message that describes the error more exactly.
408:
409: DMSDOS: ioctl: D_WRITE: no memory!
410: O: Lack of system memory. Can be ignored. (*)[see below]
411:
412: DMSDOS: ioctl: loglevel set to 0x%lx.
413: I: The message tells it all.
414:
415: DMSDOS: ioctl: read_cluster: no memory!
416: O: The driver could not read a cluster because of lack of memory. Don't run
417: so much applications at the same time, increase your swap space or add
418: memory to your machine. (Shouldn't happen.) (*)[see below]
419:
420: DMSDOS: ioctl: speedup set to 0x%lx.
421: I: The message tells it all.
422:
423: DMSDOS: killing internal daemon...
424: I: Debug message. Ignore.
425:
426: DMSDOS: list statistics:
427: I: Debug message. Ignore.
428:
429: DMSDOS: lock_ch: count=0! This is a bug.
430: P: Serious bug in cluster caching code. Please report. The system might
431: even hang completely now.
432:
433: DMSDOS: log_ccache_statistics: cannot happen.
434: DMSDOS: log_list_statistics: cannot happen.
435: B: Bug, please report.
436:
437: DMSDOS: MDFAT bad allocation (cluster %d)
438: E: Error in stacker filesystem.
439:
440: DMSDOS: mdfat cache:
441: I: Debug message, ignore.
442:
443: DMSDOS: MDFAT crosslink in CVF detected (cluster %d)
444: DMSDOS: MDFAT crosslink detected (cluster %d)
445: E: There's a MDFAT level crosslink in your compressed partition. This is a
446: serious error you should immediately repair by running dos scandisk.
447:
448: DMSDOS: MDFAT entry invalid (cluster %d, sect %d)
449: DMSDOS: MDFAT entry invalid in CVF (cluster %d)
450: DMSDOS: MDFAT entry invalid in CVF (fragmented cluster %d fragpnt %d)
451: E: There's a problem with your compressed partition. Dmsdos ignores
452: invalid entries if they are assigned to a file (the file will be
453: unreadable).
454:
455: DMSDOS: MDFAT-level dead sectors found in CVF (cluster %d)
456: DMSDOS: MDFAT-level dead sectors found, removing...
457: E/I: The driver has found sectors in the filesystem that belong to a
458: non-existing cluster. Depending on the repair flag, it tries to
459: repair the problem.
460:
461: DMSDOS: MDR signature found at sector %d
462: I: Debug message. Usually shows the number of the last sector in the CVF.
463:
464: DMSDOS: MDR test breaks at i=%d
465: I: Debug message that is produced during CVF size test. There's very
466: likely also a message 'access beyond end of device' logged just before
467: this message. It's part of the MDR test to provoke an access beyond
468: the device end. You can safely ignore both messages.
469:
470: DMSDOS: mount_dblspace: out of memory
471: O: Shouldn't happen.
472:
473: DMSDOS: mounting CVF on device 0x%x %s...
474: I: The message tells it all.
475:
476: DMSDOS: mount_stacker: out of memory
477: O: Shouldn't happen.
478:
479: DMSDOS: MOVEBACK ioctl has gone
480: O: Then don't use it.
481:
482: DMSDOS: MSDBL/MSDSP signature not found, CVF skipped
483: E: This file doesn't seem to be really a CVF. The driver refuses, for
484: example, to mount your phone directory that has been renamed to
485: something like dblspace.001. Check the compressed filesystem under
486: dos (if dos refuses to boot because it runs into a similar problem,
487: use a dos boot disk and hold down CTRL and F8 during boot process).
488:
489: DMSDOS: no memory for decompression!
490: O: The driver could not decompress a cluster because of lack of memory.
491: Don't run so much applications at the same time, increase your swap space
492: or add memory to your machine. (Shouldn't happen.) (*)[see below]
493:
494: DMSDOS: page-aligned memory returned by kmalloc - please disable XMALLOC
495: B: The xmalloc allocation mechanism is broken. This may be caused by
496: using a very new kernel. You can still use dmsdos, but you are strongly
497: encouraged to disable xmalloc: rerun the dmsdos configuration, disable
498: advanced memory management and recompile. Please send also a problem
499: report so I can start looking for what broke xmalloc in your kernel.
500:
501: DMSDOS: part 1 of filesystem check failed, aborting.
502: DMSDOS: part 2 of filesystem check failed, aborting.
503: I: The message tells it all.
504:
505: DMSDOS: read BITFAT state error
506: E: Problem with stacker filesystem. Probably low level host drive IO
507: error.
508:
509: DMSDOS: read_cluster: illegal cvf version flag!
510: B: Bug, please report.
511:
512: DMSDOS: read_cluster: mdfat sectors > sectperclust, cutting
513: E: There's an error in the filesystem. The next time you boot dos you
514: should check it (including the surface test). (This indicates a
515: corrupted MDFAT, may be suspicious to be a dmsdos write access bug.)
516:
517: DMSDOS: read_file bug: f_pos not cluster-aligned
518: B: ???
519:
520: DMSDOS: read_fragments: cluster does not look fragmented!
521: DMSDOS: read_fragments failed!
522: DMSDOS: read_fragments: safety_counter exceeds membytes!
523: E: Error in drivespace 3 filesystem. Check under Win95.
524:
525: DMSDOS: read_fragments: size limit reached.
526: I: Debug message. Ignore.
527:
528: DMSDOS: read_the_page: no memory!
529: O: Shouldn't happen.
530:
531: DMSDOS: read_virtual_sector: no memory!
532: DMSDOS: read_virtual_sector: read_cluster failed!
533: E/I: Problem with virtual sector handling.
534:
535: DMSDOS: READ/WRITE DIRENTRY ioctl has gone
536: DMSDOS: RECOMPRESS ioctl has gone
537: O: So don't use them.
538:
539: DMSDOS: sd4_comp: Compression ends with mismash
540: DMSDOS: sd4_comp: Hufman code leakage in table 1
541: DMSDOS: sd4_comp: Hufman code leakage in table 2
542: DMSDOS: sd4_huffman: Problems with number of bits
543: I: Huffman code length of some character is longer
544: than 15 bits in STAC4 compression. Code will be recomputed
545: with little worse compression ratio.
546: Message may be disabled in future.
547:
548: DMSDOS: sd4_decomp: no memory!
549: O: Data cannot be decompressed, memory is low. (See below for 'no memory'
550: messages.)
551:
552: DMSDOS: sd4_decomp: Magic = %X => error!
553: DMSDOS: sd4_decomp: Table 2 consistency check !!!!
554: DMSDOS: sd4_decomp: Table 1 consistency check !!!!
555: DMSDOS: sd4_decomp: Table 1 error
556: DMSDOS: sd4_decomp: Under !!!
557: DMSDOS: sd4_decomp: Over !!!!
558: DMSDOS: sd4_decomp: End read %X and should be %X
559: DMSDOS: sd4_decomp: Error end token %X
560: E: Data cannot be decompressed.
561: Filesystem probably damaged. Run DOS stac/check.
562:
563: DMSDOS: SETMAXCLUSTER ioctl has gone.
564: O: This ioctl command has turned out to be too dangerous. Use the native
565: CVF maintainance tools that came with your CVF package under Dos/Win95.
566:
567: DMSDOS: set_maxcluster %d refused: cluster %d in use
568: O: You tried to specify a cluster limit that is too low via the
569: 'setmaxcluster' command of dutil. This message also displays the
570: currently lowest possible value ('cluster %d in use'). Your command has
571: been skipped.
572:
573: DMSDOS: set_maxcluster refused - CVF is not in doublespace or drivespace<=2 format.
574: O: The setmaxcluster command is intended as workaround for a bug in
575: dos scandisk. You can only use it on CVFs that have been created by
576: a doublespace version that has this bug.
577:
578: DMSDOS: strange version flag %d, assuming 0.
579: I/E: The version flag in the CVF header contains garbage. Either it's
580: destroyed or you have found a new doublespace/drivespace version. In
581: the latter case please let me know.
582:
583: DMSDOS: simple_check aborted (no memory)
584: O: Lack of kernel memory caused the dmsdos driver to abort the filesystem
585: check. Shouldn't happen. (*)[see below]
586:
587: DMSDOS: simple_check: BITFAT abnormal state
588: DMSDOS: simple_check: BITFAT mounted/dirty
589: DMSDOS: simple_check: BITFAT state error
590: IE: The BITFAT/allocation map of the stacker filesystem is marked as
591: 'not up-to-date'. This may have been caused by a dos crash or reset.
592: The filesystem can only be used read-only. You can repair it by
593: booting DOS (stacker will show its "updating allocation map"
594: message) or use dmsdos' mount option 'bitfaterrs=repair' or use dutil.
595:
596: DMSDOS: simple_check: read BITFAT sumary error
597: E: Error in stacker filesystem.
598:
599: DMSDOS: simple_check: MDFAT+BITFAT test skipped (no memory)
600: O: Lack of kernel memory caused the dmsdos driver to skip the MDFAT and
601: BITFAT test. Since this test may require up to 1 MB kernel memory
602: (depending on the partition size), this message may occur occasionally.
603: You needn't be concerned about this. (*)[see below]
604:
605: DMSDOS: sq_comp: ERROR: Processed only %d bytes !!!!!!
606: DMSDOS: sq_comp: Huffman code leakage in table 1
607: DMSDOS: sq_comp: Huffman code leakage in table 2
608: DMSDOS: sq_comp: Huffman code leakage in table 3
609: DMSDOS: sq_huffman: Problems with number of bits
610: I: SQ compression problem. Data will be compressed again with lower
611: compression ratio or written without compression.
612:
613: DMSDOS: sq_comp: Not enough memory
614: O: The data written uncompressed due to lack of memory for compression.
615:
616: DMSDOS: SQ-0-0 decompression failed.
617: DMSDOS: sq_dec: huff BAD last token %x
618: DMSDOS: sq_dec: huff count_1 too big
619: DMSDOS: sq_dec: huff count_2 too big
620: DMSDOS: sq_dec: huff error in char and len table
621: DMSDOS: sq_dec: huff error in helper table
622: DMSDOS: sq_dec: huff error in offset table
623: DMSDOS: sq_dec: huff offset OVER
624: DMSDOS: sq_dec: huff offset UNDER
625: DMSDOS: sq_dec: out of memory!
626: DMSDOS: sq_dec: submethod not tested - fixed huffman
627: DMSDOS: sq_dec: unknown submethod - 3
628: E/B: Error in SQ compressed data (drivespace 3). Check under Win95.
629: I've been reported about SQ decompression problems when the files
630: even decompress well under Win95. There seems to be a problem
631: somewhere in the SQ decompression code, but I'm unable to fix it.
632:
633: DMSDOS: stac3_decomp: char repeat overrun!
634: DMSDOS: stac3_decomp: end token 0x%02X
635: DMSDOS: stac3_decomp: Illegal back pointer length 0x%x at pos 0x%x->0x%x
636: DMSDOS: stac3_decomp: Multi rep overrun 0x%x at pos 0x%x->0x%x
637: DMSDOS: stac3_decomp: ReadNC error!
638: DMSDOS: stac3_decomp: Unknown token %d on pos 0x%X->0x%X
639: DMSDOS: stac3_decomp: xor sum error!
640: E: Looks like your stacker filesystem is corrupt. The data of a file
641: couldn't be decompressed.
642:
643: DMSDOS: stac3_decomp: Multi rep:(%dx %d)
644: DMSDOS: stac3_decomp: Rep:(%dx)
645: I: Debug messages. Ignore.
646:
647: DMSDOS: stac_cwalk_init: bad bytes_in_cluster %d
648: DMSDOS: stac_cwalk_init: count = %d < 0 in long subalocated
649: DMSDOS: stac_cwalk_init: count = %d < 0 in short subalocated
650: DMSDOS: stac_cwalk_init: fragment signature not found cluster=%d
651: DMSDOS: stac_cwalk_init: sector count mismash fragmented cluster=%d!
652: DMSDOS: stac_cwalk_init: suballocation signature not found cluster=%d
653: DMSDOS: stac_cwalk_init: suballocation error 1, cluster %d
654: DMSDOS: stac_cwalk_init: suballocation error 2, cluster %d
655: DMSDOS: stac_cwalk_init: suballocation error 3, cluster %d, zerro offset 0x%X 0x%X
656: DMSDOS: stac_cwalk_init: suballocation error 4, cluster %d
657: DMSDOS: stac_cwalk_init: suballocation not present, cluster %d
658: DMSDOS: stac_cwalk_init: too much fragmented cluster=%d!
659: DMSDOS: stac_cwalk_init: unknown flags 0x%2x cluster %d
660: DMSDOS: stac_cwalk_init: wrong cluster types for subalocation, cluster %d
661: E?: Looks like your stacker filesystem is corrupt.
662:
663: DMSDOS: stac_cwalk_sector: finfo==NULL, cluster %d
664: B: Internal bug in fragmented clusters access.
665:
666: DMSDOS: Stacker 0x1A0A signature not found
667: E/O: This CVF doesn't seem to be really a CVF.
668:
669: DMSDOS: Stacker sector size not 512 bytes, hmm...
670: E: Strange error in stacker filesystem or incompatible version (?)
671:
672: DMSDOS: STACKER signature not found
673: E/O: This CVF doesn't seem to be really a CVF.
674:
675: DMSDOS: stac_read_cluster: alloc error in cluster %d
676: DMSDOS: stac_read_cluster: decompression error cluster=%d
677: DMSDOS: stac_read_cluster: internal cw error 1 cluster=%d
678: DMSDOS: stac_read_cluster: internal cw error 2 cluster=%d
679: E: Error in stacker filesystem.
680:
681: DMSDOS: stac_read_cluster: no memory!
682: O: The driver could not read a cluster because of lack of memory. Don't run
683: so much applications at the same time, increase your swap space or add
684: memory to your machine. (Shouldn't happen.) (*)[see below]
685:
686: DMSDOS: stac_replace_existing_cluster: This is a bug - reboot and check filesystem
687: B: Safety check in allocation routine failed. Please send a bug report.
688:
689: DMSDOS: stac_special_free: alloc error in cluster %d
690: E: Problems with deleting of cluster may be caused by
691: - damaged filesystem
692: should be reported when mounted as bitfat mismashes
693: can be repaired by mount option bitfaterrs=repair
694: - dmsdos internal bug
695:
696: DMSDOS: stac_write_cluster: alloc error in cluster %d
697: DMSDOS: stac_write_cluster: internal cw error 1 cluster=%d
698: DMSDOS: stac_write_cluster: internal cw error 2 cluster=%d
699: E: Error in stacker filesystem.
700:
701: DMSDOS: stac_write_cluster: no memory for compression, writing uncompressed!
702: O: Shouldn't happen.(*)[see below]
703:
704: DMSDOS: starting internal daemon...
705: I: The message tells it all.
706:
707: DMSDOS: Sumary: Deleted clusters = %d
708: DMSDOS: Sumary: Free sectors = %d
709: DMSDOS: Sumary: info1 = %d
710: DMSDOS: Sumary: info2 = %d
711: I: Internal stacker messages. Information from checking of CVF.
712: First two are counted and next two are read from CVF.
713:
714: DMSDOS: support for doublespace/drivespace(<3) not compiled in.
715: DMSDOS: support for drivespace 3 not compiled in.
716: DMSDOS: support for stacker 3 not compiled in.
717: DMSDOS: support for stacker 4 not compiled in.
718: O: The message tells it all. Rerun the dmsdos configuration and recompile
719: the source if you do need support for this type of CVF.
720:
721: DMSDOS: Too many BITFAT mismatches, check aborted.
722: DMSDOS: Too many BITFAT mismatches in CVF, check aborted.
723: E: The message tells it all.
724:
725: DMSDOS: try_daemon: kill_proc daemon_pid=%d failed with error code %d, assuming daemon has died
726: O: The driver tried to wake up the external daemon, but it seems to be no
727: longer running.
728:
729: DMSDOS: try_daemon: no empty slot found, listcount corrected.
730: B: Shouldn't happen.
731:
732: DMSDOS: try_fragmented: cnt<0 ? This is a bug.
733: DMSDOS: try_fragmented: frags=%d ? Cannot happen.
734: DMSDOS: try_fragmented returned non-free sectors!
735: B: Shouldn't happen (bugs in code for writing fragmented clusters for
736: drivespace 3 volumes).
737:
738: DMSDOS: trying to allocate fragmented space...
739: I: The driver tries to create a fragmented cluster since disk space is
740: low or highly fragmented.
741:
742: DMSDOS: unable to read acache area=%d
743: DMSDOS: unable to read bitfat area %d for sector %d
744: DMSDOS: unable to read dfat area %d for cluster %d
745: DMSDOS: unable to read emulated boot block of CVF
746: DMSDOS: unable to read mdfat area %d for cluster %d
747: DMSDOS: unable to read second dfat
748: DMSDOS: unable to read second mdfat
749: DMSDOS: unable to read super block
750: DMSDOS: unable to read super block of CVF
751: E: Bad block or serious error in the underlying msdos filesystem. The
752: CVF or the underlying filesystem is most likely destroyed.
753:
754: DMSDOS: unable to read fragmentation list of cluster %d.
755: E: Error in drivespace 3 filesystem or hardware error.
756:
757: DMSDOS: unknown option %s, rejected
758: O: Syntax error in mount option string.
759:
760: DMSDOS: Updating BITFAT
761: DMSDOS: Updating BITFAT.
762: DMSDOS: Updating BITFAT finished
763: DMSDOS: version_flag=%d sectperclust=%d
764: I: Debug info.
765:
766: DMSDOS: vmalloc returned unaligned memory - please disable XMALLOC
767: P/B: The xmalloc allocation mechanism is broken. This may be caused by
768: using a very new kernel. The driver detected this problem and stopped
769: immediately to prevent memory corruption. You may have to press the
770: reset button after this message. You can still use dmsdos, but you must
771: disable xmalloc before: rerun dmsdos configuration and disable advanced
772: memory management. Please send also a problem report so I can start
773: looking for what broke xmalloc in your kernel.
774:
775: DMSDOS: write access not compiled in, ignored
776: I: Someone or something tried to write to a compressed partition but write
777: access support is not compiled in. This message always appeares
778: *instead* of a real write access.
779:
780: If you *want* to write to a compressed partition, you must compile
781: in write access support before. Rerun the dmsdos configuration
782: ('make config' in the src directory), recompile and reinstall dmsdos.
783:
784: DMSDOS: write_cluster: guessed 0x%08x.
785: I: The driver succeeded to guess the compression method and tells what
786: it has guessed.
787:
788: DMSDOS: write_cluster: guessing compression method...
789: I: The driver is analysing some clusters to determine the compression
790: method automatically. This kind of 'guessing' has proven to be very
791: reliable, so it may be a good idea to let the driver guess the
792: compression method instead of specifying it explicitely in a mount
793: option.
794:
795: DMSDOS: write_cluster: illegal cvf_version flag!
796: B: Looks like a bug in the dmsdos configuration (some missing or wrong
797: ifdefs somewhere). Let me know, please. Meanwhile, configure dmsdos
798: to support everything, recompile, and try again.
799:
800: DMSDOS: write_cluster: no memory for compression, writing uncompressed!
801: I: The driver could not compress a cluster because of lack of memory, so
802: it skipped compression. Don't run so much applications at the same time,
803: increase your swap space or add memory to your machine. (Shouldn't
804: happen.) (*)[see below]
805:
806: DMSDOS: write_file: ch_dirty failed!
807: DMSDOS: write_file: ch_noread failed
808: DMSDOS: write_file: ch_noread failed!
809: E: There should be another message describing the error.
810:
811: DMSDOS: write_file: CVF full (free sector count too low)
812: DMSDOS: write_file: CVF full (full flag set)
813: O: Guess what. To prevent filesystem corruption, the driver has stopped
814: write access at a cluster boundary and returned the 'no space left on
815: device' error code in order to give an application the chance to exit
816: cleanly.
817:
818: WARNING: As you cannot exactly say how well the data compress it is
819: dangerous to fill a CVF up to the last byte. The driver tries to stop
820: applications quite a time before it becomes dangerous. This message
821: indicates that up to now nothing dangerous has happened.
822:
823: DMSDOS: write_file: length>clustersize ??? bug !!!
824: B: Cannot happen.
825:
826: DMSDOS: write_file: fat_add_cluster failed
827: O: Filesystem is full or has run out of clusters. Run dutil to distinguish
828: between these two situations. In the latter case you need to boot dos
829: and increase the estimated compression ratio.
830:
831: DMSDOS: write_file: read_cluster failed!
832: E: There should be another message describing the error.
833:
834: DMSDOS: write_file: something wrong, cannot happen
835: DMSDOS: write_file: something's wrong, cannot happen
836: B: Problem with writing a file.
837:
838: DMSDOS: write_fragmented: raw_getblk sector %d failed
839: O/B: Low-level disk i/o problem or serious bug (may even be a bug in
840: the rest of the kernel). A fragmented cluster couldn't be written.
841: This leaves behind a damaged filesystem. You must repair it under
842: Win95 (if it is a real hardware error, e.g. dying disk, you might
843: be lost hopelessly without a backup).
844:
845: DMSDOS: unable to read emulated boot block
846: E: Error in filesystem, check it under dos.
847:
848: DMSDOS: zero_new_cluster: ch_noread failed???
849: O/B: Don't know. Really. This shouldn't happen.
850:
1.1.1.2 ! root 851: VFS: LRU list corrupted
! 852: VFS: free list corrupted
! 853: (or similar)
! 854: P/B/O: You are very suffering from the vfat brelse bug (this is a serious
! 855: bug in some 2.2.x and maybe late 2.1.x kernels). This bug is triggered
! 856: by dmsdos. Ensure you have applied the vfat-brelse-bugfix.diff or you
! 857: are using a kernel where the bug is fixed (in 2.2.2 it is not yet fixed).
! 858: See file patches/DIFFS.TXT or INSTALL.TXT for details.
! 859:
! 860: If not, this indicates probably a leak in dmsdos virtual sector code.
! 861: Please send a bug report to the current dmsdos maintainer and be prepared
! 862: to be asked for some tests in order to track down the bug.
! 863:
1.1 root 864: (*) ['no memory' messages:]
865: There was a problem in previous dmsdos versions that caused these
866: messages rarely though there was enough memory free. I've tried to fix
867: it by calling another memory allocation routine in newer dmsdos
868: releases. It's currently unknown if the new method is better. So if
869: you think you receive 'no memory' messages too often, you can try to
870: switch the allocation mode. It's setup during dmsdos configuration
871: ('make config'). If you change it, please let me know your results.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.