- Storage - lists.openanolis.cn

by Joseph Qi

Hi All, The next sig teleconference is scheduled on Nov 23, 2022. Join link: https://meeting.dingtalk.com/j/lpwTSmoEhER Join code: 528 808 30423 Duration: 11:00 ~ 12:00 CST Topics: 1. Sig programs updates. 2. DSMS introduction by Linx Software. 3. Technical discussion (if any). Thanks, Joseph

1 year, 5 months

1
0
0 0

Re: [anolis] How to Setup NFS Server on Anolis OS 8.6?

by Joseph Qi

Hi Ziyang, Could you please help take a look? Thanks, Joseph On 11/10/22 10:31 PM, Yong Wu wrote: > How to Setup NFS Server on Anolis OS 8.6? > Hi all. I can successfully setup NFS server on RHEL/CentOS 8, but the same operation is not successful on Anolis OS 8.6. > > [root@master ~]# rpm -qa|egrep "nfs-utils|rpcbind" > rpcbind-1.2.5-8.0.1.an8.x86_64 > nfs-utils-2.3.3-51.0.1.an8.x86_64 > > > [root@master ~]# systemctl status nfs-server.service > ● nfs-server.service - NFS server and services > Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled) > Drop-In: /run/systemd/generator/nfs-server.service.d > └─order-with-mounts.conf > Active: active (exited) since Thu 2022-11-10 21:38:04 CST; 44min ago > Process: 1216 ExecStart=/bin/sh -c if systemctl -q is-active gssproxy; then systemctl reload gssproxy ; fi (code=exited, status=0/SUCCE> > Process: 1201 ExecStart=/usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS) > Process: 1191 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS) > Main PID: 1216 (code=exited, status=0/SUCCESS) > > > Nov 10 21:38:04 master systemd[1]: Starting NFS server and services... > Nov 10 21:38:04 master systemd[1]: Started NFS server and services. > > > > [root@master ~]# systemctl status nfs-utils.service > ● nfs-utils.service - NFS server and client services > Loaded: loaded (/usr/lib/systemd/system/nfs-utils.service; static; vendor preset: disabled) > Active: active (exited) since Thu 2022-11-10 21:44:56 CST; 38min ago > Process: 3494 ExecStart=/bin/true (code=exited, status=0/SUCCESS) > Main PID: 3494 (code=exited, status=0/SUCCESS) > > > Nov 10 21:44:56 master systemd[1]: Starting NFS server and client services... > Nov 10 21:44:56 master systemd[1]: Started NFS server and client services. > > > > [root@master ~]# systemctl status firewalld.service > ● firewalld.service - firewalld - dynamic firewall daemon > Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled) > Active: inactive (dead) > Docs: man:firewalld(1) > > > > [root@master ~]# getsebool > getsebool: SELinux is disabled > > > > [root@master ~]# ifconfig ens224 > ens224: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 10.1.1.1 netmask 255.255.0.0 broadcast 10.1.255.255 > inet6 fe80::20c:29ff:febe:108b prefixlen 64 scopeid 0x20<link> > ether 00:0c:29:be:10:8b txqueuelen 1000 (Ethernet) > RX packets 470 bytes 32638 (31.8 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 472 bytes 33040 (32.2 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > [root@master ~]# cat /etc/exports > /opt 10.1.0.0/16(rw,insecure,no_root_squash,sync) > /home 10.1.0.0/16(rw,insecure,no_root_squash,sync) > > > > [root@master ~]# rpcinfo |grep nfs > 100003 3 tcp 0.0.0.0.8.1 nfs superuser > 100003 4 tcp 0.0.0.0.8.1 nfs superuser > 100227 3 tcp 0.0.0.0.8.1 nfs_acl superuser > 100003 3 tcp6 ::.8.1 nfs superuser > 100003 4 tcp6 ::.8.1 nfs superuser > 100227 3 tcp6 ::.8.1 nfs_acl superuser > > > > Get the following errors: > [root@master ~]# showmount -e master > rpc mount export: RPC: Unable to receive; errno = Connection refused > > > Can anyone give me some advice? > > > Best regards, > Yong Wu > > > --- > Faculty of Chemistry > Northeast Normal University > Renmin Street No.5268 > Changchun, Jilin 130024 > P. R. China. > > > > > > > > _______________________________________________ > Anolis OS mailing list -- os(a)lists.openanolis.cn > To unsubscribe send an email to os-leave(a)lists.openanolis.cn

1 year, 6 months

2
1
0 0

Re: [ck]Re: cgroup2 io weight 没有效果

by Joseph Qi

Hi, Which cgroup version do you use? cgroup v1 or v2? For bfq, I don't have any experience on weight control. For iocost, better to specify qos and model, according to the documentation suggested before. Seems you've mixed bfq, iocost, block throttle together. I'd suggest you evaluate them individually and use direct io first. Thanks, Joseph On 9/29/22 3:26 PM, 王传国 wrote: > Hi Joseph, > Thanks for your reply! But I have 2 questions, : > 1. why the blkio.bfq.weight has no effect after "echo bfq > /sys/block/vdb/queue/scheduler" > 2.iocost didn't work either, two fio both got 5M,but 3M and 6M is what I want.Point out my mistakes please! > Thanks very much! > And my shell like below: > > mount /dev/vdb1 /wcg/data2/ > > cd /sys/fs/cgroup/blkio > > echo bfq > /sys/block/vdb/queue/scheduler > > echo 0 > /sys/block/vdb/queue/iosched/low_latency > > echo "253:16 10485760" > blkio.throttle.write_bps_device > > echo "253:16 enable=1" > blkio.cost.qos > > echo "253:16 ctrl=auto" > blkio.cost.model > > echo 0 > /sys/block/vdb/queue/rotational > > mkdir fio1 fio2 > > echo "253:16 100" > fio1/blkio.cost.weight > > echo "253:16 200" > fio2/blkio.cost.weight > > > > > echo $$ > /sys/fs/cgroup/blkio/fio1/cgroup.procs > > fio -rw=write -ioengine=libaio -bs=4k -size=1G -numjobs=1 -name=/wcg/data2/fio_test1.log > > > > > #do follows at another console > > echo $$ > /sys/fs/cgroup/blkio/fio2/cgroup.procs > > fio -rw=write -ioengine=libaio -bs=4k -size=1G -numjobs=1 -name=/wcg/data2/fio_test2.log > > > > > > > > > > > > 在 2022-09-28 16:41:40，"Joseph Qi" <joseph.qi(a)linux.alibaba.com> 写道： >> 'io.weight' is for cfq io scheduler, while 'io.bfq.weight' is for bfq io >> scheduler, as its name indicates. >> So you may need configure corresponding io scheduler as well. >> >> BTW, if you want io weight control, I recommend another approach named io >> cost. The following documentation may help to understand the details: >> https://help.aliyun.com/document_detail/155863.html >> >> Thanks, >> Joseph >> >> On 9/28/22 1:50 PM, 王传国 wrote: >>> 各位同仁, >>> >>> 我看到cgroup2中有io.weight 和 io.bfq.weight，区别是什么? >>> >>> 我的理解是为了控制兄弟group在父group下的IO权重，我在如下版本测试了下，好像结果不太对，谁能指点一下，拜谢！ >>> >>> # uname -a >>> >>> Linux localhost.localdomain 4.19.91-26.an8.x86_64 #1 SMP Tue May 24 13:10:09 CST 2022 x86_64 x86_64 x86_64 GNU/Linux >>> >>> >>> >>> 我的测试脚本： >>> >>> #change to cgroup2 by adding cgroup_no_v1=all into grub param >>> >>> mkdir -p /aaa/cg2 >>> >>> mkdir -p /aaa/data2 >>> >>> mount -t cgroup2 nodev /aaa/cg2 >>> >>> mount /dev/sdb1 /aaag/data2/ >>> >>> echo bfq > /sys/block/vdb/queue/scheduler #做或不做 >>> >>> >>> >>> mkdir /aaa/cg2/test >>> >>> echo "+io +memory" > /aaa/cg2/cgroup.subtree_control >>> >>> echo "+io +memory" > /aaa/cg2/test/cgroup.subtree_control >>> >>> cat /aaa/cg2/test/cgroup.controllers >>> >>> echo "8:16 wbps=10485760" > /aaa/cg2/test/io.max >>> >>> echo $$ > /aaa/cg2/test/cgroup.procs >>> >>> >>> >>> mkdir -p /aaa/cg2/test/dd1 >>> >>> mkdir -p /aaa/cg2/test/dd2 >>> >>> echo 200 > /aaa/cg2/test/dd1/io.weight >>> >>> #echo 200 > /aaa/cg2/test/dd1/io.bfq.weight #两个选项都试了 >>> >>> >>> >>> #在另外2个终端执行如下的2个测试: >>> >>> echo $$ > /aaa/cg2/test/dd1/cgroup.procs >>> >>> dd if=/dev/zero of=/aaa/data2/ddfile1 bs=128M count=1 >>> >>> >>> >>> echo $$ > /aaa/cg2/test/dd2/cgroup.procs >>> >>> dd if=/dev/zero of=/aaa/data2/ddfile2 bs=128M count=1 >>> >>> >>> >>> 我得到了两个 500K+, 而不是期望的300K+ and 600K！ >>> >>> >>> >>> _______________________________________________ >>> Cloud Kernel mailing list -- cloud-kernel(a)lists.openanolis.cn >>> To unsubscribe send an email to cloud-kernel-leave(a)lists.openanolis.cn >> _______________________________________________ >> Cloud Kernel mailing list -- cloud-kernel(a)lists.openanolis.cn >> To unsubscribe send an email to cloud-kernel-leave(a)lists.openanolis.cn

1 year, 7 months

3
11
0 0

SIG Regular Teleconference

by 韩光宇

Hi all, The next sig teleconference is scheduled on Sep 14, 2022. Join Link: dingtalk://dingtalkclient/page/videoConfFromCalendar?confId=45655e96-7b25-4ec9-8984-7f39d4d3d0a1&calendarId=1960345551 Join Code: 415 981 62308 Duration:  11:00 ~ 12:00 CST Regular topics: 1. Sig programs updates. 2. Technical discussion (if any). Anyone has other topics, please feedback. Thanks, Han Guangyu _______________________________________________ Storage mailing list -- storage(a)lists.openanolis.cn To unsubscribe send an email to storage-leave(a)lists.openanolis.cn

1 year, 8 months

1
0
0 0

Sig teleconference topics collection

by 王磊

Hi all, The next sig teleconference is scheduled on Aug 17, 2022. Join Link: dingtalk://dingtalkclient/page/videoConfFromCalendar?confId=8d1f1b83-8df8-4b92-bcdf-90fbfcfb808b&calendarId=1914092942 Join Code: 385 647 36460 Duration: 11:00 ~ 12:00 CST Regular topics: 1. Sig programs updates. 2. Technical discussion (if any). If anyone has some other topics, please feedback. Thanks, Wang Lei _______________________________________________ Storage mailing list -- storage(a)lists.openanolis.cn To unsubscribe send an email to storage-leave(a)lists.openanolis.cn

1 year, 9 months

1
0
0 0

SIG teleconference topics collection

by Gao Xiang

Hi all, The next SIG teleconference is scheduled on Aug 3, 2022. Join Link: dingtalk://dingtalkclient/page/videoConfFromCalendar?confId=efd177c1-26cc-4dc6-a39f-31f8a2d62279&calendarId=1895077931 Join Code: 369 179 22300 Duration: 11:00 ~ 12:00 CST Regular topics: 1. Sig programs updates. 2. Technical discussion (if any). If anyone has some other topics, please feedback. Thanks, Gao Xiang

1 year, 9 months

1
0
0 0

SIG Regular Teleconference

by Joseph Qi

Hi All, The next SIG regular teleconference is scheduled on Jul 6, 2022. Join link: dingtalk://dingtalkclient/page/videoConfFromCalendar?confId=ae913769-804c-470f-8ac6-efa54634e767&calendarId=1852451710 Join code: 319 500 50137 Duration: 11:00 ~ 12:00 CST Regular topics: 1. Sig programs updates. 2. Technical discussion (if any). Anyone has other topics, please feedback. Thanks, Joseph

1 year, 10 months

2
1
0 0

Sig teleconference topics collection

by 王磊

Hi all, The next sig teleconference is scheduled on Jun 22, 2022. Join Link: dingtalk://dingtalkclient/page/videoConfFromCalendar?confId=04865b6d-8843-4c83-991c-73a2685eff03&calendarId=1659823097 Join Code: 294 121 33291 Duration: 11:00 ~ 12:00 CST Regular topics: 1. Sig programs updates. 2. Technical discussion (if any). If anyone has some other topics, please feedback. Thanks, Wang Lei _______________________________________________ Storage mailing list -- storage(a)lists.openanolis.cn To unsubscribe send an email to storage-leave(a)lists.openanolis.cn

1 year, 11 months

1
0
0 0

SIG Regular Teleconference

by Joseph Qi

Hi All, The next SIG regular teleconference is scheduled on Jun 8, 2022. Join link: dingtalk://dingtalkclient/page/videoConfFromCalendar?confId=7e6b20ff-9ed8-441d-a3df-146122e48bda&calendarId=1789744649 Join code: 281 557 65565 Duration: 11:00 ~ 12:00 CST Regular topics: 1. Sig programs updates. 2. Technical discussion (if any). Anyone has other topics, please feedback. Thanks, Joseph

1 year, 11 months

1
0
0 0

SIG Regular Teleconference

by Joseph Qi

Hi all, The next SIG regular teleconference is scheduled on May 11, 2022. Join link: dingtalk://dingtalkclient/page/videoConfFromCalendar?confId=68c3c12f-d8d2-4b50-a1ee-99d96bd45e84&calendarId=1753999837 Join code: 233 087 08072 Duration: 11:00 ~ 12:00 CST Regular topics: 1. Sig programs updates. 2. Technical discussion (if any). Anyone has other topics, please feedback. Thanks, Joseph

2 years

1
0
0 0

2024

2023

2022

2021

Storage