On Tue, Sep 26, 2006 at 03:47:28PM +0300, Dan Shimshoni wrote: > Did anyone had success with this ?
Ok, I took a quick look at it. It appears that mkufs and fs/ufs/ do not agree about the superblock location and/or the magic number: UFSD (/home/muli/w/iommu/calgary/linux/fs/ufs/super.c, 612): ufs_fill_super:ENTER UFSD (/home/muli/w/iommu/calgary/linux/fs/ufs/super.c, 620): ufs_fill_super:flag 1 UFSD (/home/muli/w/iommu/calgary/linux/fs/ufs/super.c, 306): ufs_parse_options:ENTER You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep .. >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old UFSD (/home/muli/w/iommu/calgary/linux/fs/ufs/super.c, 707): ufs_fill_super:ufstype=old ufs_read_super: bad magic number 0x0 UFSD (/home/muli/w/iommu/calgary/linux/fs/ufs/super.c, 1045): ufs_fill_super:EXIT (FAILED) The next step would be to check both against a UFS spec and verify whether the disk image indeed has a superblock at the right location and that the superblock contains the right magic number. If it doesn't, it's mkufs's fault. If it does, it's the kernel's fault. Happy debugging! Cheers, Muli ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
