Thu, 14 Dec 2006 you wrote:

> > # mount_ext2fs /dev/wd0g /mnt  
> > mount_ext2fs: /dev/wd0g on /mnt: incorrect super block
> > # mount_ext2fs /dev/wd0g /mnt -o ro
> > usage: mount_ext2fs [-o options] special node
> > # mount_ext2fs -o ro /dev/wd0g /mnt 
> > mount_ext2fs: /dev/wd0g on /mnt: incorrect super block
> Was your ext3 filesystem cleanly unmounted under Linux?

Yes. Sure. When fs was not unmounter propertly, netbsd mounts this
volume with a warning that i need to run fsck on this volume.

here is the list of supported features by each volume:

root@ds:~# tune2fs -l /dev/hda2|grep fea
Filesystem features:      has_journal filetype needs_recovery
sparse_super
root@ds:~# tune2fs -l /dev/hda3|grep fea
Filesystem features:      has_journal resize_inode filetype
needs_recovery sparse_super large_file

hda2 mount perfect under netbsd, but hda3 not.

The strange this occured yesterday. yesterday i disable dir_index
feature and then netbsd mount disk again. But after reboot it can't use
it again.

Alex