* error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize [not found] <S1752440Ab1APNtL/20110116134911Z+826@vger.kernel.org> @ 2011-01-16 14:03 ` Stuart Pook 2011-01-16 14:28 ` Stuart Pook 0 siblings, 1 reply; 5+ messages in thread From: Stuart Pook @ 2011-01-16 14:03 UTC (permalink / raw) To: linux-ext4 hi I'm getting these errors on my home filesystem [ 5147.616006] EXT4-fs (dm-28): error count: 11 [ 5147.616888] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 [ 5147.617827] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 I have done a fsck -f and that didn't make them stop. The errors started a few minutes after I did an online resize of my filesystem. To resize the filesystem I did something like this: lvextend --size +14G vg_root/stuart cryptsetup resize _dev_dm_21 resize2fs /dev/mapper/_dev_dm_21 It took me a couple of attemps to find the correct arguments for the "cryptsetup resize" but I don't think I broke anything. When I saw the errors from "mv" at 12:32:46 I unmounted the filesystem and did a fsck. That corrected some errors but I'm still getting "ext4_mb_generate_buddy:726" and "add_dirent_to_buf:1272" errors. The filesystem in question is an encrypted partition on top of a lvm partition on a SSD. thanks Stuart :; uname -a Linux kooka 2.6.37-trunk-amd64 #1 SMP Thu Jan 6 14:13:28 UTC 2011 x86_64 GNU/Linux :; fsck.ext4 -V e2fsck 1.41.12 (17-May-2010) Using EXT2FS Library version 1.41.12, 17-May-2010 :; grep 'EXT4-fs.*error' /var/log/syslog Jan 16 12:32:46 kooka kernel: : [2379819.157537] EXT4-fs error (device dm-27): ext4_mb_generate_buddy:726: group 3232766 blocks in bitmap, 32254 in gd Jan 16 12:32:46 kooka kernel: : [2379819.157840] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:32:46 kooka kernel: : [2379819.158226] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:32:46 kooka kernel: : [2379819.158500] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:32:46 kooka kernel: : [2379819.158520] EXT4-fs error (device dm-27): ext4_free_blocks:4591: comm mv: Freeing blocks in system zone - Block = 1048579, count = 1 Jan 16 12:32:46 kooka kernel: : [2379819.158769] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:32:46 kooka kernel: : [2379819.158784] EXT4-fs error (device dm-27): ext4_free_blocks:4591: comm mv: Freeing blocks in system zone - Block = 1048580, count = 1 Jan 16 12:32:46 kooka kernel: : [2379819.159003] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:32:46 kooka kernel: : [2379819.159216] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:32:46 kooka kernel: : [2379819.159449] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:32:46 kooka kernel: : [2379819.159464] EXT4-fs error (device dm-27): ext4_free_blocks:4591: comm mv: Freeing blocks in system zone - Block = 1048581, count = 1 Jan 16 12:32:46 kooka kernel: : [2379819.159679] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:32:46 kooka kernel: : [2379819.159907] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:32:46 kooka kernel: : [2379819.159923] EXT4-fs error (device dm-27): ext4_free_blocks:4591: comm mv: Freeing blocks in system zone - Block = 1048582, count = 1 Jan 16 12:32:46 kooka kernel: : [2379819.160154] EXT4-fs error (device dm-27): add_dirent_to_buf:1272: inode #262145: block 1048578: comm mv: bad entry in directory: inode out of bounds - offset=0(0), inode=65552832, rec_len=4096, name_len=0 Jan 16 12:55:05 kooka kernel: : [2381158.368007] EXT4-fs (dm-18): error count: 11 Jan 16 12:55:05 kooka kernel: : [2381158.368020] EXT4-fs (dm-18): initial error at 1295177566: ext4_mb_generate_buddy:726 Jan 16 12:55:05 kooka kernel: : [2381158.368030] EXT4-fs (dm-18): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 Jan 16 13:05:23 kooka kernel: : [2381775.840005] EXT4-fs (dm-18): error count: 11 Jan 16 13:05:23 kooka kernel: : [2381775.840009] EXT4-fs (dm-18): initial error at 1295177566: ext4_mb_generate_buddy:726 Jan 16 13:05:23 kooka kernel: : [2381775.840012] EXT4-fs (dm-18): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 Jan 16 13:19:47 kooka kernel: : [ 364.512007] EXT4-fs (dm-28): error count: 11 Jan 16 13:19:47 kooka kernel: : [ 364.512392] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 Jan 16 13:19:47 kooka kernel: : [ 364.512776] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 Jan 16 13:42:54 kooka kernel: : [ 1752.032005] EXT4-fs (dm-28): error count: 11 Jan 16 13:42:54 kooka kernel: : [ 1752.032010] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 Jan 16 13:42:54 kooka kernel: : [ 1752.032014] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 Jan 16 14:39:30 kooka kernel: : [ 5147.616006] EXT4-fs (dm-28): error count: 11 Jan 16 14:39:30 kooka kernel: : [ 5147.616888] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 Jan 16 14:39:30 kooka kernel: : [ 5147.617827] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize 2011-01-16 14:03 ` error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize Stuart Pook @ 2011-01-16 14:28 ` Stuart Pook 2011-01-29 22:15 ` Stuart Pook 0 siblings, 1 reply; 5+ messages in thread From: Stuart Pook @ 2011-01-16 14:28 UTC (permalink / raw) To: linux-ext4 I forgot to mention: I am now running kooka 2.6.37-trunk-amd64 but when I resized the filesystem and started getting the errors I was running linux-image-2.6.37-rc5-amd64. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize 2011-01-16 14:28 ` Stuart Pook @ 2011-01-29 22:15 ` Stuart Pook 2011-01-29 22:33 ` Ted Ts'o 0 siblings, 1 reply; 5+ messages in thread From: Stuart Pook @ 2011-01-29 22:15 UTC (permalink / raw) To: linux-ext4 I am getting these message about once a day. Each message arrives 24 hours amd a few minuted after the last message, wierd. Inode 262145 is a directory that I created just after the online resize of the filesystem. I have emptied the directory. Should I remove it? Or should I rebuild the filesystem? Thanks for any advice :; zgrep 'EXT4-fs.*error' /var/log/syslog* /var/log/syslog:Jan 29 17:57:21 kooka kernel: : [1125159.904008] EXT4-fs (dm-28): error count: 11 /var/log/syslog:Jan 29 17:57:21 kooka kernel: : [1125159.904014] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 /var/log/syslog:Jan 29 17:57:21 kooka kernel: : [1125159.904017] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 /var/log/syslog.1:Jan 28 17:55:34 kooka kernel: : [1038652.384009] EXT4-fs (dm-28): error count: 11 /var/log/syslog.1:Jan 28 17:55:34 kooka kernel: : [1038652.384015] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 /var/log/syslog.1:Jan 28 17:55:34 kooka kernel: : [1038652.384018] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 /var/log/syslog.2.gz:Jan 27 17:53:46 kooka kernel: : [952144.864006] EXT4-fs (dm-28): error count: 11 /var/log/syslog.2.gz:Jan 27 17:53:46 kooka kernel: : [952144.864012] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 /var/log/syslog.2.gz:Jan 27 17:53:46 kooka kernel: : [952144.864015] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 /var/log/syslog.3.gz:Jan 26 17:51:59 kooka kernel: : [865637.344007] EXT4-fs (dm-28): error count: 11 /var/log/syslog.3.gz:Jan 26 17:51:59 kooka kernel: : [865637.344013] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 /var/log/syslog.3.gz:Jan 26 17:51:59 kooka kernel: : [865637.344017] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 /var/log/syslog.4.gz:Jan 25 17:50:11 kooka kernel: : [779129.824008] EXT4-fs (dm-28): error count: 11 /var/log/syslog.4.gz:Jan 25 17:50:11 kooka kernel: : [779129.824014] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 /var/log/syslog.4.gz:Jan 25 17:50:11 kooka kernel: : [779129.824018] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 /var/log/syslog.5.gz:Jan 24 17:48:24 kooka kernel: : [692622.304007] EXT4-fs (dm-28): error count: 11 /var/log/syslog.5.gz:Jan 24 17:48:24 kooka kernel: : [692622.304013] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 /var/log/syslog.5.gz:Jan 24 17:48:24 kooka kernel: : [692622.304017] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 /var/log/syslog.6.gz:Jan 23 17:46:36 kooka kernel: : [606114.784006] EXT4-fs (dm-28): error count: 11 /var/log/syslog.6.gz:Jan 23 17:46:36 kooka kernel: : [606114.784012] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 /var/log/syslog.6.gz:Jan 23 17:46:36 kooka kernel: : [606114.784015] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 /var/log/syslog.7.gz:Jan 22 17:44:49 kooka kernel: : [519607.264009] EXT4-fs (dm-28): error count: 11 /var/log/syslog.7.gz:Jan 22 17:44:49 kooka kernel: : [519607.264015] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 /var/log/syslog.7.gz:Jan 22 17:44:49 kooka kernel: : [519607.264018] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize 2011-01-29 22:15 ` Stuart Pook @ 2011-01-29 22:33 ` Ted Ts'o 2011-02-01 11:45 ` Stuart Pook 0 siblings, 1 reply; 5+ messages in thread From: Ted Ts'o @ 2011-01-29 22:33 UTC (permalink / raw) To: Stuart Pook; +Cc: linux-ext4 On Sat, Jan 29, 2011 at 11:15:56PM +0100, Stuart Pook wrote: > I am getting these message about once a day. Each message arrives 24 hours amd a few minuted after the last message, wierd. Inode 262145 is a directory that I created just after the online resize of the filesystem. Sorry for my lack of response. I've been in Brisbane for the past week attending linux.conf.au. This message which you are seeing: > /var/log/syslog:Jan 29 17:57:21 kooka kernel: : [1125159.904008] EXT4-fs (dm-28): error count: 11 > /var/log/syslog:Jan 29 17:57:21 kooka kernel: : [1125159.904014] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726 > /var/log/syslog:Jan 29 17:57:21 kooka kernel: : [1125159.904017] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578 ... is strictly speaking not an error. It is a status report indicating that in the past your file system had suffered an error. The first error was at 1295177566 seconds past the epoch, or at: % date -d @1295177566 Sun Jan 16 06:32:46 EST 2011 ...and the most recent error was at: % date -d @1295177566 Sun Jan 16 06:32:46 EST 2011 If you upgrade to e2fsck 1.41.14, it will reset the error counter and the first/last most recent errors. The idea behind this is that sometimes people aren't paying close attention to their /var/log/messages file, so this is a periodic informational reminder, printed once a day. If you are creating shell scripts to find errors, match on "EXT4-fs Error", for example "EXT4-fs error (dm-28): disk on fire". Warnings will be denoted with "EXT4-fs warning", and and information messages, such as this one just start with "EXT4-fs", as in "EXT4-fs (dm-28): ..." Hope this helps, - Ted ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize 2011-01-29 22:33 ` Ted Ts'o @ 2011-02-01 11:45 ` Stuart Pook 0 siblings, 0 replies; 5+ messages in thread From: Stuart Pook @ 2011-02-01 11:45 UTC (permalink / raw) To: Ted Ts'o; +Cc: linux-ext4 On 29/01/11 23:33, Ted Ts'o wrote: > ... is strictly speaking not an error. It is a status report > indicating that in the past your file system had suffered an error. > The first error was at 1295177566 seconds past the epoch, or at: > > % date -d @1295177566 > Sun Jan 16 06:32:46 EST 2011 :; date -d @1295177566 Sun Jan 16 12:32:46 CET 2011 It's little later in my timezone and that was just after I resized my file system. > If you upgrade to e2fsck 1.41.14, it will reset the error counter and > the first/last most recent errors. I upgraded to 1.41.14, ran e2fsck and the messages have stopped. We still don't know what caused the initial errors (which have now vanished). As they started just after an online resize I'd guess that there were (are?) some bugs in that code. I'll avoid doing online resizes of my ext4 file systems for the moment. > The idea behind this is that > sometimes people aren't paying close attention to their > /var/log/messages file, so this is a periodic informational reminder, > printed once a day. That's a good idea. Once you know how to translate 1295177566 into a real time, you can go and look in the logs for the correct day. > If you are creating shell scripts to find errors, > match on "EXT4-fs Error", for example "EXT4-fs error (dm-28): disk on > fire". Warnings will be denoted with "EXT4-fs warning", and and > information messages, such as this one just start with "EXT4-fs", as > in "EXT4-fs (dm-28): ..." perhaps it would be better if they started with "EXT4-fs repeat message" (or something that you might be able to find with google) > Hope this helps, It sure does, thanks Stuart ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-02-01 11:45 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <S1752440Ab1APNtL/20110116134911Z+826@vger.kernel.org>
2011-01-16 14:03 ` error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize Stuart Pook
2011-01-16 14:28 ` Stuart Pook
2011-01-29 22:15 ` Stuart Pook
2011-01-29 22:33 ` Ted Ts'o
2011-02-01 11:45 ` Stuart Pook
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.