<pre>>and that would be which kernel and drbd version/revision exactly?<br>>(sorry, no 10.2 handy right now)<br><br>Kernel: 2.6.18.2-34 (x86) SMP<br>Although I've tried slightly older kernel too (the one from suse
<br>10.1) dont have it handy though.<br><br>DRBD version:<br>"out of the box" - 0.7.22-30<br><br>>and if you do this without drbd,<br>>it does behave fine, presumably?<br><br>It works fine without drbd, yes.
<br><br><br>>what is in kernel log before "read-only file system" ?<br>>any oopes, BUG()s, stacktraces or drbd related messages?<br><br>no errors in the kernel log or messages, no traces, no bugs, no errors.
<br><br><br>>what file system?<br><br>ext3. I've never been able to get drbd to work with anything else.<br><br>>does it happen<br>> without drbd ?<br>Yes!<br>> with drbd StandAlone?<br>Yes!<br>> with drbd Connected?
<br><br>Yes!<br><br>In fact, I've nailed it down a bit, to do "quick testing"<br>I created a test directory as follows (as root):<br><br>mkdir /test<br>cd /test<br>mkdir A<br>tar -cvf test.tar .<br><br>then copied this 10k tar file to the partition I just setup with DRBD,
<br><br>and tried to untar it.<br><br>DRBD will "crash" every time! By this I mean, it cannot create the directory,<br>and instantly puts the partition into "read-only mode"<br><br>Every single time.<br>
<br><br>I can untar hundreds of megs, of thousands of files, and it's fine.<br>But try and untar a single directory, and wham! every time.<br><br>what's up with this? weirder and weirder.<br><br>>did you run memtest
<br><br><br>No, but I'm not sure how this applies. the system runs perfectly without DRBD.<br>such a small simple test, it's not ram.<br><br>Dan.</pre>