On Tue, 2005-10-11 at 00:31 +0200, Jan Engelhardt wrote:
> >> > is it working for anyone? I've set it to 20, and i'm either getting
> >> > nothing or just small bits of junk.
> >>
> >> Yep I've seen junk too. At first I thought it was a buffer
> >> overrun/overwrite, but that can't be since printk takes an appropriate
> >> spinlock.
> >>
> > Hello,
> > What do you mean by junk? Also where are you looking for the debug
>
> Junk aka chars below 0x20. It's like it's trying to print
> int blah = 13371337;
> printf("%s\n", (char *)&blah);
> that sort of "junk".
>
> > information? We haven't come across any problems with out fist_debug output
> > but
> > I cant say with 100% certainty that there isn't one.
>
> Set debug level to 20, run `klogconsole -l8 -r0` and work with a union
> mount. If it generates lots of output (read: screenfuls) than reduce the
> debug level stepwise to 17 until it is very moderate (like 2
> msgs/screenful or even less) and then do something like
> tar -cvjf /dev/null /union/usr/src/linux, something that stats and touches
> many files. Reading is enough.
My problem is different, I set it to 20 and I got nothing besides small
amounts of junk.
_______________________________________________
unionfs mailing list
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
