search for: __ext3_std_error

Hi! I tried to use cdrdao on 2.5.5x kernels but kernel gives me following messages. Further debugging reveals that sb is NULL in __ext3_std_error() function. I tried this on ext2 and it seems it isn't ext3 specific, on ext2 it also doesn't work. cdrdao is after this in D state and is unkillable, but the CD-ROM drive from which I tried to grab is perfectly usable. This happens to me only with cdrdao, otherwise system is perfectly...

...rtition claiming it contained errors. During the check it found: Deleted inode 142279 has zero dtime. FIXED. The kernel message log contained lots of: EXT3-fs error (device md(9,1)) in ext3_new_inode: error 28 We had used up all the available inodes. Since the above message is generated from __ext3_std_error, it marks the filesystem bad. This doesn't sound like proper behaviour. Kernel: Red Hat 2.4.9-21 -- Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html

...ree, + unsigned *five, unsigned *seven) { unsigned *min = three; int mult = 3; --- linux-2.6.10-mm2-full/include/linux/ext3_fs.h.old 2005-01-06 23:23:16.000000000 +0100 +++ linux-2.6.10-mm2-full/include/linux/ext3_fs.h 2005-01-06 23:27:28.000000000 +0100 @@ -793,25 +793,15 @@ extern void __ext3_std_error (struct super_block *, const char *, int); extern void ext3_abort (struct super_block *, const char *, const char *, ...) __attribute__ ((format (printf, 3, 4))); -extern NORET_TYPE void ext3_panic (struct super_block *, const char *, - const char *, ...) - __attribute__ ((NORET_AND format...