Hello, I''m running Xen 3.0.4 on a test server and I''ve been having several file system corruption problems using the tap:aio driver. This message shows up in dmesg on different machines. EXT2-fs error (device sda1): ext2_check_page: bad entry in directory #114914: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 EXT2-fs error (device sda1): ext2_readdir: bad page in #114914 If I change to the loopback driver the problem goes away. Any ideas on what would cause this? Is this going to be fixed in 3.0.5? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 4/9/07, Michael Watters <michael@watters.ws> wrote:> If I change to the loopback driver the problem goes away. > > Any ideas on what would cause this? Is this going to be fixed in 3.0.5?Is it a xen from xensource or some distribution packages? If the problem is reproducible, you should report a bug in the xen bugzilla (or, if you use distribution packages, in the distribution''s bug tracking system, first). Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Henning Sprang wrote:> On 4/9/07, Michael Watters <michael@watters.ws> wrote: >> If I change to the loopback driver the problem goes away. >> >> Any ideas on what would cause this? Is this going to be fixed in 3.0.5? > > Is it a xen from xensource or some distribution packages?I''m using the RPMs from xensource. I''ve also noticed I/O errors when running commands that create a lot of disk activity, "emerge sync" results in a corrupted partition every time. I''ll see if I can file a bug report on it. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users