From cf0156ae86a5887f102d343e0c979c3518e12b2e Mon Sep 17 00:00:00 2001 From: Masanori Kobayasi Date: Wed, 3 Oct 2012 12:37:47 +0900 Subject: [PATCH] Release docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt [JF:20125] --- docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt | 171 +++++++++++++++++++++ .../filesystems/gfs2-uevents.txt.info | 7 + lists/kdoc-2.6-reserved.list | 10 +- www/news.m4 | 3 + 4 files changed, 186 insertions(+), 5 deletions(-) create mode 100644 docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt create mode 100644 docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt.info diff --git a/docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt b/docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt new file mode 100644 index 0000000..435ae87 --- /dev/null +++ b/docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt @@ -0,0 +1,171 @@ +========================================================= +¤³¤ì¤Ï¡¢ +Linux-3.4.1/Documentation/filesystems/gfs2-uevents.txt ¤ÎÏÂÌõ¤Ç¤¹¡£ +ËÝÌõÃÄÂΡ§ JF ¥×¥í¥¸¥§¥¯¥È < http://linuxjf.sourceforge.jp/ > +¹¹¿·Æü ¡§ 2012/07/04 +ËÝÌõ¼Ô ¡§ Seiji Kaneko < skaneko at a2 dot mbn dot or dot jp > +========================================================= +# uevents and GFS2 +# ================== + uevent ¤È GFS2 + ============== + +#During the lifetime of a GFS2 mount, a number of uevents are generated. +#This document explains what the events are and what they are used +#for (by gfs_controld in gfs2-utils). +GFS2 ¤¬¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤ë´Ö¤Ë¤Ï¡¢ÍÍ¡¹¤Ê uevent ¤¬À¸À®¤µ¤ì¤Þ¤¹¡£¤³¤Îʸ½ñ¤Ç¤Ï¡¢ +event ¤ÎÆâÍƤȻÈÍÑÌÜŪ (gfs2-utils ¤Î gfs_controld) ¤òÀâÌÀ¤·¤Þ¤¹¡£ + +#A list of GFS2 uevents +#----------------------- +GFS2 ¤Î uevent ¤Î¥ê¥¹¥È +----------------------- + +#1. ADD +1. ADD + +#The ADD event occurs at mount time. It will always be the first +#uevent generated by the newly created filesystem. If the mount +#is successful, an ONLINE uevent will follow. If it is not successful +#then a REMOVE uevent will follow. +ADD ¥¤¥Ù¥ó¥È¤Ï¥Þ¥¦¥ó¥È»þ¤ËȯÀ¸¤·¤Þ¤¹¡£¤³¤ì¤Ï¾ï¤Ë¿·¤·¤¯ºîÀ®¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¥·¥¹ +¥Æ¥à¤ÎºÇ½é¤Î uevent ¤Ë¤Ê¤ê¤Þ¤¹¡£¥Þ¥¦¥ó¥È¤¬¤¦¤Þ¤¯¤¤¤Ã¤¿¾ì¹ç¡¢¤½¤Î¸å¤Ë ONLINE +uevent ¤¬Â³¤­¤Þ¤¹¡£¥Þ¥¦¥ó¥È¤¬¤¦¤Þ¤¯¤¤¤«¤Ê¤«¤Ã¤¿¾ì¹ç¤Ë¤Ï¡¢REMOVE uevent +¤¬Â³¤­¤Þ¤¹¡£ + +#The ADD uevent has two environment variables: SPECTATOR=[0|1] +#and RDONLY=[0|1] that specify the spectator status (a read-only mount +#with no journal assigned), and read-only (with journal assigned) status +#of the filesystem respectively. +ADD uevent ¤ÏÆó¤Ä¤Î´Ä¶­ÊÑ¿ô¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¾õÂÖ¤¬¡¢ +spectator ¥¹¥Æ¡¼¥¿¥¹ (¥¸¥ã¡¼¥Ê¥ë¤¬»ØÄꤵ¤ì¤Ê¤¤¥ê¡¼¥É¥ª¥ó¥ê¡¼¥Þ¥¦¥ó¥È) ¤Ë¤¢ +¤ë¤³¤È¤ò¼¨¤¹ SPECTATOR=[0|1] ¤È¡¢read-only ¥¹¥Æ¡¼¥¿¥¹ (¥¸¥ã¡¼¥Ê¥ë»ØÄêºÑ¤ß¤Î +¥ê¡¼¥É¥ª¥ó¥ê¡¼¥Þ¥¦¥ó¥È) ¤Ë¤¢¤ë¤³¤È¤ò»ØÄꤹ¤ë RDONLY=[0|1] ¤Ç¤¹¡£ + +#2. ONLINE +2. ONLINE + +#The ONLINE uevent is generated after a successful mount or remount. It +#has the same environment variables as the ADD uevent. The ONLINE +#uevent, along with the two environment variables for spectator and +#RDONLY are a relatively recent addition (2.6.32-rc+) and will not +#be generated by older kernels. +ONLINE uevent ¤Ï¥Þ¥¦¥ó¥È (¤Þ¤¿¤ÏºÆ¥Þ¥¦¥ó¥È) À®¸ù¸å¤ËÀ¸À®¤µ¤ì¤Þ¤¹¡£¤³¤ì¤Ï +ADD uevent ¤ÈƱ¤¸ 2 ¤Ä¤Î´Ä¶­ÊÑ¿ô¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£ONLINE uevent ¤È¡¢ +spectator/RDONLY ´Ä¶­ÊÑ¿ô¤ÏÈæ³ÓŪºÇ¶á (2.6.32-rc+) Äɲ䵤줿¤â¤Î¤Ç¤¢¤ê¡¢ +¤½¤ì¤è¤ê¸Å¤¤¥«¡¼¥Í¥ë¤Ç¤ÏÀ¸À®¤µ¤ì¤Þ¤»¤ó¡£ + +#3. CHANGE +3. CHANGE + +#The CHANGE uevent is used in two places. One is when reporting the +#successful mount of the filesystem by the first node (FIRSTMOUNT=Done). +#This is used as a signal by gfs_controld that it is then ok for other +#nodes in the cluster to mount the filesystem. +CHANGE uevent ¤Ï¡¢2 ¤Ä¤Î¾ì¹ç¤ÇÍѤ¤¤é¤ì¤Þ¤¹¡£°ìÊý¤Ï¡¢ºÇ½é¤Î¥Î¡¼¥É¤Ç¥Õ¥¡¥¤¥ë +¥·¥¹¥Æ¥à¤Î¥Þ¥¦¥ó¥È¤¬À®¸ù¤·¤¿¤³¤È¤ÎÊó¹ð (FIRSTMOUNT=Done) ¤Ç¤¹¡£¤³¤ì¤Ï¡¢ +gfs_controld ¤Ç¡¢CLUSTER¤ò¹½À®¤¹¤ë¾¤Î¥Î¡¼¥É¤«¤éÅö³º¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò +mount ¤Ç¤­¤ë¤³¤È¤ò¼¨¤¹¥·¥°¥Ê¥ë¤È¤·¤ÆÍѤ¤¤é¤ì¤Þ¤¹¡£ + +#The other CHANGE uevent is used to inform of the completion +#of journal recovery for one of the filesystems journals. It has +#two environment variables, JID= which specifies the journal id which +#has just been recovered, and RECOVERY=[Done|Failed] to indicate the +#success (or otherwise) of the operation. These uevents are generated +#for every journal recovered, whether it is during the initial mount +#process or as the result of gfs_controld requesting a specific journal +#recovery via the /sys/fs/gfs2//lock_module/recovery file. +¤â¤¦¤Ò¤È¤Ä¤Î CHANGE uevent ¤Ï¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¸¥ã¡¼¥Ê¥ë¤Î¤¦¤Á¤Î°ì¤Ä¤Ç¥¸ +¥ã¡¼¥Ê¥ë²óÉü¤¬´°Î»¤·¤¿¤³¤È¤òÊó¹ð¤¹¤ë¤¿¤á¤ËÍѤ¤¤é¤ì¤Þ¤¹¡£¤³¤Î¥·¥°¥Ê¥ë¤Ï 2 ¤Ä +¤Î´Ä¶­ÊÑ¿ô¤ò»ý¤Á¤Þ¤¹¡£JID= ¤Ï²óÉü¤ËÍѤ¤¤¿¥¸¥ã¡¼¥Ê¥ë¤Î id ¤ò¼¨¤·¤Þ¤¹¡£ +RECOVERY=[Done|Failed] ¤Ï²óÉü½èÍý¤ÎÀ®¸ù/¼ºÇÔ¤ò¼¨¤·¤Þ¤¹¡£¤³¤Î uevent ¤Ï¡¢½é +´ü¥Þ¥¦¥ó¥È½èÍý¤ÎºÝ¤È¡¢/sys/fs/gfs2//lock_module/recovery ¥Õ¥¡¥¤¥ë¤ò +ÍѤ¤¤ÆÆÃÄê¤Î¥¸¥ã¡¼¥Ê¥ë¤Î²óÉü¤ò gfs_controld ¤Ë»Ø¼¨¤·¤¿¾ì¹ç¤Î·ë²Ì¤È¤·¤Æ¡¢²ó +ÉüÂоݤΥ¸¥ã¡¼¥Ê¥ë¤´¤È¤ËȯÀ¸¤·¤Þ¤¹¡£ + +#Because the CHANGE uevent was used (in early versions of gfs_controld) +#without checking the environment variables to discover the state, we +#cannot add any more functions to it without running the risk of +#someone using an older version of the user tools and breaking their +#cluster. For this reason the ONLINE uevent was used when adding a new +#uevent for a successful mount or remount. +°ÊÁ°¤Ï CHANGE uevent ¤¬¡¢¾õÂÖ¤òÇÄ°®¤¹¤ë¤¿¤á¤Î´Ä¶­ÊÑ¿ô¤Î¥Á¥§¥Ã¥¯¤Ê¤·¤ËÍѤ¤ +¤é¤ì¤Æ¤¤¤¿¤¿¤á (gfs_controld ¤Î½é´ü¤ÎÈǤÇ)¡¢¤³¤ì°Ê¾å¤Îµ¡Ç½¤òÄɲ乤뤳¤È¤Ç +狼¤¬µìÈǤΥ桼¥¶¥Ä¡¼¥ë¤òÍѤ¤¤Æ¥¯¥é¥¹¥¿¤òÇ˲õ¤¹¤ë´í¸±¤òÈȤ¹¤ï¤±¤Ë¤Ï¹Ô¤­¤Þ +¤»¤ó¤Ç¤·¤¿¡£¤³¤Î¤¿¤á¡¢mount ¤ä remount ¤ÎÀ®¸ù¤ò¼¨¤¹¡¢¿·µ¬¤Î ONLINE uevent +¤¬Äɲ䵤ì¤Æ¤¤¤Þ¤¹¡£ + +#4. OFFLINE +4. OFFLINE + +#The OFFLINE uevent is only generated due to filesystem errors and is used +#as part of the "withdraw" mechanism. Currently this doesn't give any +#information about what the error is, which is something that needs to +#be fixed. +OFFLINE uevent ¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¨¥é¡¼¤Î¤¿¤á¤À¤±¤ËÀ¸À®¤µ¤ì¡¢¡ÖÄü¤á¤ë +(withdraw)¡×¥á¥«¥Ë¥º¥à¤Î°ìÉô¤È¤·¤ÆÍѤ¤¤é¤ì¤Þ¤¹¡£¸½¾õ¤Ç¤Ï¡¢¤³¤Î uevent ¤Ï¡¢ +½¤Àµ¤Î¤¿¤á¤Ë²¿¤é¤«¤ÎÌò¤ËΩ¤Ä¤è¤¦¤Ê¡¢¥¨¥é¡¼¤ÎÆâÍƤò¼¨¤¹¾ðÊó¤Ï²¿¤âÄ󶡤·¤Þ¤» +¤ó¡£ + +#5. REMOVE +5. REMOVE + +#The REMOVE uevent is generated at the end of an unsuccessful mount +#or at the end of a umount of the filesystem. All REMOVE uevents will +#have been preceded by at least an ADD uevent for the same filesystem, +#and unlike the other uevents is generated automatically by the kernel's +#kobject subsystem. +REMOVE uevent ¤Ï¥Þ¥¦¥ó¥È¤Î¼ºÇԤκݤνªÎ»»þ¡¢¤ª¤è¤Ó¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î unmount +½èÍý¤Î½ªÎ»»þ¤ËÀ¸À®¤µ¤ì¤Þ¤¹¡£REMOVE uevent ¤ÎÁ°¤Ë¤Ï¡¢É¬¤º³ºÅö¥Õ¥¡¥¤¥ë¥·¥¹¥Æ +¥à¤Ë´Ø¤¹¤ë ADD uevent ¤¬¾¯¤Ê¤¯¤È¤â¤Ò¤È¤Ä¤Ï¤¢¤ë¤Ï¤º¤Ç¤¹¡£¤Þ¤¿¡¢Â¾¤Î uevent +¤È¤Ï°Û¤Ê¤ê¡¢¤³¤Î uevent ¤Ï¥«¡¼¥Í¥ë¤Î kobject ¥µ¥Ö¥·¥¹¥Æ¥à¤Ç¼«Æ°Åª¤ËÀ¸À®¤µ¤ì +¤Þ¤¹¡£ + + +#Information common to all GFS2 uevents (uevent environment variables) +#---------------------------------------------------------------------- +GFS2 uevent ¤Ç¶¦Ä̤˻Ȥï¤ì¤ë¾ðÊó (uevent ´Ä¶­ÊÑ¿ô) + +#1. LOCKTABLE= +1. LOCKTABLE= + +#The LOCKTABLE is a string, as supplied on the mount command +#line (locktable=) or via fstab. It is used as a filesystem label +#as well as providing the information for a lock_dlm mount to be +#able to join the cluster. +LOCKTABLE ¤Ï¡¢mount ¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¿ô (locktable=)¡¢¤Þ¤¿¤Ï fstab ¥Ñ¥é¥á¡¼ +¥¿¤È¤·¤ÆÍ¿¤¨¤é¤ì¤¿Ê¸»úÎó¤Ç¤¹¡£¤³¤ì¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥é¥Ù¥ë¤È¤·¤ÆÍѤ¤¤é¤ì¡¢ +¹¹¤Ë lock_dim ¥Þ¥¦¥ó¥È¤Ç¥¯¥é¥¹¥¿»²²Ã¤ò¹Ô¤¦¤¿¤á¤Î¾ðÊó¤ÎÄ󶡤ËÍѤ¤¤é¤ì¤Þ¤¹¡£ + +#2. LOCKPROTO= +2. LOCKPROTO= + +#The LOCKPROTO is a string, and its value depends on what is set +#on the mount command line, or via fstab. It will be either +#lock_nolock or lock_dlm. In the future other lock managers +#may be supported. +LOCKTABLE ¤Ï¡¢mount ¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¿ô¡¢¤Þ¤¿¤Ï fstab ¥Ñ¥é¥á¡¼¥¿¤È¤·¤ÆÀßÄê +¤µ¤ì¤¿Ê¸»úÎó¤Ç¤¹¡£¤³¤ì¤Ï lock_nolock ¤Þ¤¿¤Ï lock_dim ¤Î¤¤¤º¤ì¤«¤Ç¤¹¡£¾­Íè +¤Ï¾¤Î¥í¥Ã¥¯¥Þ¥Í¡¼¥¸¥ã¤â¥µ¥Ý¡¼¥È¤µ¤ì¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£ + +#3. JOURNALID= +3. JOURNALID= + +#If a journal is in use by the filesystem (journals are not +#assigned for spectator mounts) then this will give the +#numeric journal id in all GFS2 uevents. +¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¥¸¥ã¡¼¥Ê¥ë¤òÍѤ¤¤Æ¤¤¤ë¾ì¹ç (spectator mount ¤Ç¤Ï¥¸¥ã¡¼¥Ê +¥ë¤Ï³ä¤êÅö¤Æ¤é¤ì¤Þ¤»¤ó)¡¢¤³¤ÎÃͤˤÏÁ´ GFS2 uevent ¤Ç¥¸¥ã¡¼¥Ê¥ë¤Î¿ôÃÍ id ¤¬ +ÀßÄꤵ¤ì¤Þ¤¹¡£ + +#4. UUID= +4. UUID= + +#With recent versions of gfs2-utils, mkfs.gfs2 writes a UUID +#into the filesystem superblock. If it exists, this will +#be included in every uevent relating to the filesystem. +Èæ³ÓŪºÇ¶á¤ÎÈǤΠgfs2-utils ¤Ç¤Ï¡¢mkfs.gfs2 ¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¹¡¼¥Ñ¥Ö¥í +¥Ã¥¯¤Ë UUID ¤ò½ñ¤­¹þ¤ß¤Þ¤¹¡£UUID ¤¬½ñ¤«¤ì¤Æ¤¤¤¿¾ì¹ç¤Ë¤Ï¡¢¤½¤ÎÃͤ¬Åö³º¥Õ¥¡ +¥¤¥ë¥·¥¹¥Æ¥à¤Ë´ØÏ¢¤¹¤ëÁ´¤Æ¤Î uevent ¤ÇÀßÄꤵ¤ì¤Þ¤¹¡£ + + diff --git a/docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt.info b/docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt.info new file mode 100644 index 0000000..60534ec --- /dev/null +++ b/docs/kernel-docs-2.6/filesystems/gfs2-uevents.txt.info @@ -0,0 +1,7 @@ +TITL: gfs2-uevents +CONT: Linux global file system ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î uevent ¤Î²òÀâ +NAME: filesystems/gfs2-uevents.txt +JDAT: 2012/10/02 +BVER: 3.4.1 +AUTH: unknown +TRNS: Seiji Kaneko < skaneko at a2 dot mbn dot or dot jp > diff --git a/lists/kdoc-2.6-reserved.list b/lists/kdoc-2.6-reserved.list index fd2ede2..5e79a56 100644 --- a/lists/kdoc-2.6-reserved.list +++ b/lists/kdoc-2.6-reserved.list @@ -624,11 +624,11 @@ PDAT: 2012/07/13 STAT: Draft NOTE: [JF:20102] -NAME: filesystems/gfs2-uevents.txt -TRNS: skaneko@a2.mbn.or.jp -PDAT: 2012/07/13 -STAT: Draft -NOTE: [JF:20103] +# NAME: filesystems/gfs2-uevents.txt +# TRNS: skaneko@a2.mbn.or.jp +# PDAT: 2012/07/13 +# STAT: Release +# NOTE: [JF:20103] NAME: filesystems/btrfs.txt TRNS: skaneko@a2.mbn.or.jp diff --git a/www/news.m4 b/www/news.m4 index 9188b3f..166d125 100644 --- a/www/news.m4 +++ b/www/news.m4 @@ -45,6 +45,9 @@ m4_define(`_NEW_DOC',` ')
+_NEW_DOC(kernel-docs-2.6/filesystems/gfs2-uevents.txt.html,2012/10/03, + `kernel-3.4.1 ÉÕ° filesystems/gfs2-uevents.txt ¤ÎÆüËܸìÌõ') + _NEW_DOC(kernel-docs-2.6/filesystems/gfs2.txt.html,2012/10/02, `kernel-3.6 ÉÕ° filesystems/gfs2.txt ¤ÎÆüËܸìÌõ') -- 2.11.0