Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, Jan 26, 2004 at 02:12:21PM +0100, Francis SOUYRI wrote: > >On Mon, Jan 26, 2004 at 11:03:03AM +0100, Francis SOUYRI wrote: > >>In the /var/lib/drbd/drbd.conf.parsed I see that you set the > >>"drbdX:fsckcmd fsck -p -y" if you use a journaling filesystem (reiserfs, > >>ext3, xfs, jfs) you can set it to "drbdX:fsckcmd /bin/true". > >Good idea, but there was no fsck running and journaling filesystems also > >need a fsck every now and then as the journal only prevents problems at > >reboots without clean unmounts but does not care about bit errors and > >corrupt filesystems etc that do (out of experience) seldomly. Especially > >on a Maildir-based mailserver system. > > > Escuse me I do not understand: "that do (out of experience) seldomly". > > You normaly need a fsck on a journaling filesystem when you have a > hardware problem (bit errors, dead blocks), but with drbd, when you have ... DRBD works at block device layer. Thus, if for some reason, the kernel writes a corrupt information on it, it gets replicated even if it is not conform to the filesystem specs. The drbd panic only helps if the error is one of the kind that the hardware realizes and reports back to the kernel drbd driver as problem. bye, -christian- -- Christian Hammers WESTEND GmbH | Internet-Business-Provider Technik CISCO Systems Partner - Authorized Reseller Lütticher Straße 10 Tel 0241/701333-11 ch at westend.com D-52064 Aachen Fax 0241/911879