On Jul 12, 2011, at 3:18 PM, Mike Frysinger wrote: > when i read the kernel source, that seemed to be the case. but i dont > think it's the case for reiserfs, and i think there's a very tiny edge > case with ext[34] related to moving the journal, but probably so small > we can ignore it :p. What do you think the edge case is? Yes, the external journal's dev_t is cached, but that is only used by the kernel since it was simpler than having callouts to a userspace daemon. E2fsck will use blkid to locate the external journal, and when it finds it, it will update the cached dev_t if it is out of date, so that at mount time the kernel will be able to find the external journal. This way even if the external journal is on a device with an unstable dev_t (e.g., a USB device), the right thing should happen... -- Ted -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
