Hi,
We are writing a block driver for a raid controller similar to the DAC960 driver. The driver is working fine. We are able to dd successfully & even verified the data that we wrote by reading it back. fdisk & mke2fs goes through normally & does'nt report any error.
$ fdisk /dev/rd/c0d0p1
$ mke2fs -b 4096 -R stride=16 -i 16384 -s 1 /dev/rd/c0d3p1
However when we try to mount the filesystem on the disk, it reports the following errors
$ mount /dev/rd/c0d3p1 /mnt
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Superblock in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block bitmap for group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #1 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #2 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #3 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #5 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #8 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #9 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #11 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #12 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #13 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #14 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #15 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #16 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #17 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #18 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #19 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #20 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #21 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #22 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #23 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #24 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #25 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #26 of the inode table in group 0 is marked free
.
.
.
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #240 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #241 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #242 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #243 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #244 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #245 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #246 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #247 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #248 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #249 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Block #250 of the inode table in group 0 is marked free
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Wrong free blocks count for group 0, stored = 31862, counted = 17272
EXT2-fs error (device rd(48,25)): ext2_check_blocks_bitmap: Wrong free blocks count in super block, stored = 31862, counted = 17272
EXT2-fs error (device rd(48,25)): ext2_check_inodes_bitmap: Wrong free inodes count in group 0, stored = 8021, counted = 4200
EXT2-fs error (device rd(48,25)): ext2_check_inodes_bitmap: Wrong free inodes count in super block, stored = 8021, counted = 4200
EXT2-fs error (device rd(48,25)): free_inode: reserved inode or nonexistent inode
and it creates a mnt file of the foll form:
$ ls -ld /mnt
?rwsrwsrwt 0 root 65535 4294967295 Jan 1 1970 mnt
^^^^^^^^^^^^^---> The date is also wrong
on issuing
$ umount /mnt
EXT2-fs error (device rd(48,25)): free_inode: reserved inode or nonexistent inode
But mount does'nt succeeds by mounting the filesystem onto the mount point.
Sometimes mount succeeds(with the same errors as above), in that case, in the mount point we are able to see the "lost+found" directory. However, if we try to create a file by doing a touch it says that there is "no space left on the device". But, creating a directory on the filesystem goes through. After creating the directory, we are able to create files on the filesystem. After unmounting the filesystem, when we again try to mount, then the files that we initially created in the disk were not present. Have anybody experienced similar kind of problems while writing a block driver for a raid device?? Any pointers on the problem would be of great help.
thanks in advance
Shyam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:18 EST