https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=127420
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|Open |Closed
Resolution|--- |Unable to Reproduce
--- Comment #10 from [email protected] ---
Let’s see if this is still reproducible on 15.1
Playbook, on a zfs based FreeBSD 15.1 bhyve vm with 4G RAM and 2 cores
sudo zfs create -V 10G zroot/datasets/vol1
sudo zfs create -V 10G zroot/datasets/vol2
sudo gmirror label -b prefer gjournaltest /dev/zvol/zroot/datasets/vol{1,2}
sudo gjournal load
sudo gjournal label /dev/mirror/gjournaltest
sudo newfs -J /dev/mirror/gjournaltest.journal
sudo mount -o async /dev/mirror/gjournaltest.journal /mnt
Checking the mount
mount -t ufs -v
/dev/mirror/gjournaltest.journal on /mnt (ufs, asynchronous, local, gjournal,
writes: sync 162 async 18474, reads: sync 5620 async
16398, fsid 5e51426aeb24ec10, vnodes: count 3 )
Preparing and executing the test
sudo mkdir -p /mnt/testdata
sudo chown nobody /mnt/testdata
sudo bonnie++ -c $(nproc) -s $(( $(sysctl -n hw.realmem) / 1048576 * 2)) -r $((
$(sysctl -n hw.realmem) / 1048576)) -u nobody
-d /mnt/testdata
Using uid:65534, gid:65534.
Writing a byte at a time...done
Writing intelligently...done
Rewriting...done
Reading a byte at a time...done
Reading intelligently...done
start 'em...done...done...done...done...done...
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...done.
Create files in random order...done.
Stat files in random order...done.
Delete files in random order...done.
Version 1.98 ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Name:Size etc /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
fbsd-x64.niet 8G::2 416k 94 121m 11 125m 13 655k 82 824m 42 7018 142
Latency 411ms 2009ms 718ms 229ms 502ms 154ms
Version 1.98 ------Sequential Create------ --------Random Create--------
fbsd-x64.niet.verwe -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
Latency 4225us 3701us 121us 4274us 123us 137us
1.98,1.98,fbsd-x64.niet.verweg.com,2,1782723177,8G,,8192,5,416,94,124206,11,127673,13,655,82,844269,42,7018,142,16,,,,,+++++,+++,++
+++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,411ms,2009ms,718ms,229ms,502ms,154ms,4225us,3701us,121us,4274us,123us,137us
No panic anymore, closing it as no (longer) reproducible. I also believe that
except for 32bit systems with limited memory or slow (usb/memory card) storage
zfs has superseded this particular usage scenario
--
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.