On Tue, Sep 08, 2009 at 04:25:53PM -0400, Jeff Blank wrote: > Hi, > > My 8.0-BETA4/amd64 installation panicked when I attempted to create a > file on zvol-backed UFS. This installation is otherwise UFS-free, ZFS > v13 w/gptzfsboot method linked from wiki, single zpool mirror > (ad{4,6}p3). > > # zfs create -V 18G z0/ufs0 > # newfs -U -L oldbender /dev/zvol/z0/ufs0 > # mount /dev/ufs/oldbender /old > # touch /old/foo > > The system usually panics immediately, but once it waited a few > seconds to do so, and I saw the file had been created. The file was > not there upon reboot in all cases, and the filesystem was considered > clean by fsck. > > Should I expect this to work? And/or is it a known issue? (Didn't > find any similar-looking problems by googling or browsing list > archives.) > > Please let me know if I need to provide more details. [...] > fs = /old > panic: ffs_sync: rofs mod I have no idea why UFS thinks file system is read-only. I'm not able to reproduce your problem. Doing some stress tests on UFS on top of ZVOL seems to work for me. Is there anything unusual in your setup? Maybe you could mail: # zpool status # zpool list # zfs get -r all -- Pawel Jakub Dawidek http://www.wheel.pl pjd_at_FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am!
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:55 UTC