Date: Thu, 22 Nov 2007 14:36:09 +0200 From: Toomas Aas <toomas.aas@raad.tartu.ee> To: freebsd-stable@freebsd.org Subject: garbled gjournal messages in dmesg with 7.0-BETA3 Message-ID: <474577B9.7090104@raad.tartu.ee>
next in thread | raw e-mail | index | archive | help
Hello! I have an IBM System x3400 machine with IBM ServeRAID 8k controller. There are three RAID1 volumes on the controller, which the OS sees as aacd0, aacd1 and aacd2. aacd1 contains three slices, aacd1s1 is simple UFS2, aacd1s2 and aacd1s3 are using UFS2 with gjournal. When I was using RELENG_7 from 20071112, there were following messages during booting regarding the gjournal: kernel: GEOM_JOURNAL: Journal 161627211: aacd1s2 contains data. kernel: GEOM_JOURNAL: Journal 161627211: aacd1s2 contains journal. kernel: GEOM_JOURNAL: Journal aacd1s2 clean. kernel: GEOM_JOURNAL: Journal 3372893522: aacd1s3 contains data. kernel: GEOM_JOURNAL: Journal 3372893522: aacd1s3 contains journal. kernel: GEOM_JOURNAL: Journal aacd1s3 clean. kernel: GEOM_JOURNAL: BIO_FLUSH not supported by aacd1s2. kernel: GEOM_JOURNAL: BIO_FLUSH not supported by aacd1s3. kernel: WARNING: Expected rawoffset 0, found 514080 kernel: WARNING: Expected rawoffset 0, found 42443730 Now I updated RELENG_7 today (20071119), and upon rebooting there are some garbled messages: kernel: GEOM_JOURNAL: Journal 161627211: aacd1s2 contains data. kernel: GEOM_JOURNAL: Journal 161627211: aacd1s2 contains journal. kernel: GEOM_JOURNAL: Journal aacd1s2 clean. kernel: GEOM_JOURNAL: Journal 3372893522: aacd1s3G EcOoMn_tJaOiUnRsN AdLa:t aB.IO kernel: _GFELOUMS_HJ OnUoRtN AsLu:p pJoorutrenda lb y 3a3a7c2d819s325.22 kernel: : aacd1s3 contains journal. kernel: GEOM_JOURNAL: Journal aacd1s3 clean. kernel: GEOM_JOURNAL: BIO_FLUSH not supported by aacd1s3. kernel: WARNING: Expected rawoffset 0, found 514080 kernel: WARNING: Expected rawoffset 0, found 42443730 The filesystem on aacd1s3.journal was mounted successfully and files seem to be intact, (but I haven't really verified all the files). This doesn't happen on every reboot, but it did happen on 2 tries out of 10. Before today's updating of RELENG_7 the machine had been rebooted 14 times and the problem had never happened. Has anyone else seen something like this? What more can I do to maybe get some useful information for developers? -- Toomas Aas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?474577B9.7090104>