Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hallo, I had some bad expieriences in the morning. I found the problem at least when reiserfs set the filesystem to read only without drbd being notified that there was something wrong. ------------------------------------------------------------------------- May 5 07:54:03 archivehost kernel: attempt to access beyond end of device May 5 07:54:03 archivehost kernel: drbd0: rw=0, want=31581104, limit=31471272 May 5 07:54:03 archivehost kernel: ReiserFS: drbd0: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [37921 37922 0x0 SD] May 5 07:54:03 archivehost kernel: klogd 1.4.1, ---------- state change ---------- May 5 07:54:09 archivehost kernel: attempt to access beyond end of device May 5 07:54:09 archivehost kernel: drbd0: rw=0, want=31581104, limit=31471272 May 5 07:54:09 archivehost kernel: ReiserFS: drbd0: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [37921 37922 0x0 SD] May 5 07:54:14 archivehost kernel: attempt to access beyond end of device May 5 07:54:14 archivehost kernel: drbd0: rw=0, want=31581104, limit=31471272 May 5 07:54:14 archivehost kernel: ReiserFS: drbd0: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [37921 37922 0x0 SD] ---------------------------------------------------------------------------- That was the end of processing on this host then !!!!!!!! ---------------------------------------------------------------------------- May 5 10:01:33 archivehost kernel: REISERFS: abort (device drbd0): Journal write error in flush_commit_list May 5 10:01:33 archivehost kernel: REISERFS: Aborting journal for filesystem on drbd0 May 5 10:01:33 archivehost kernel: ReiserFS: drbd0: warning: clm-6006: writing inode 148501 on readonly FS May 5 10:01:33 archivehost last message repeated 2 times ---------------------------------------------------------------------------- With 'drbdadm down drive01' and manual mount of /home (previous /dev/drbd0 ->/home) system came back to life. Is there something wrong in the filesystem configuration ? Gerhard