| Issue 37: | IOCTL interface | |
| 1 person starred this issue and may be notified of changes. | Back to list |
This is the ioctl interface that the OHSM will have.Currently we are implementing 10 ioctl's.We can further add more to it. 1. TIER INFORMATION 2. ASSIGN TIER DEVICE INFORMATION 3. ASSIGN ALLOCATION POLICY 4. ASSIGN RELOCATION POLICY 5. OHSM ENABLED 6. OHSM DISABLED 7. SHOW CURRENT POLICY BOTH ALLOC & RELLOC 8. REASSIGN ALLOC POLICY 9. REASSIGN RELOC POLICY 10 REASSIGN TIER DEVICE INFORMATION Kindly look into this issues and provide necessary feedbacks.
Jan 24, 2009
Project Member
#1
sandeepksinha
Jan 29, 2009
Dude.... Kindly update this issue with the recent changes that are being planned/made.
Jan 29, 2009
Currently 2 new ioctls have been added to this. 1.SHOWING EXISTING LOGICAL VOLUME AND THE UNDERLYING DEVICES 2.CREATING LOGICAL VOLUME WITH THE USER GIVING THE DEVICES AS PARAMETER Accordingly changes are being done to the code getopt.c
Jan 29, 2009
Rohit... Good !!! Any timelines that you think, when you should be able to finish this off by ?
Jan 29, 2009
I have attached a file regarding the issue.It has the necessary changes.The 2 ioctls has been served.I am yet to decide over the 1st one(case in user enters the existing ioctl).
Jan 29, 2009
I have attached a file.Just go thru the quoated text in FLAG_LVU and FLAG_LVC. Plz have a lookas what to do next.I am not able to proceed.
Jan 29, 2009
We have provided with a option to see the underlying devices under the LVM.The script we have takes input the logical volume name and provides us with the underlying devices.We can provide this but do we really need this because admin knows about pvscan ,lvscan and vgscan and he can easily find this out seeing the output of these commands(atleast frm CLI point of view).Just have a look.
Jan 30, 2009
Sir have a look at the code.It is working for the 2 cases i.e 1.for using the existing lvm 2.creating a new lvm getopt.c is the final code for this fs_lvm is the script which creates the lvm a.sh is your script
Jan 30, 2009
If you have verified the code. Copy paste the logs here, submit the code to TL and close this issue. Open issue for the DOCS and start working on the same.
Jan 30, 2009
THe logs have been copy pasted. [root@localhost sam]# ./ohsm -u /dev/vg/lvol0 option u This ioctl gives the information about the logical volume and devices beneath Arguments are /dev/vg/lvol0 /dev/vg/lvol0 /dev/sda7 We would display the name of the underlying devices within the LVM you have enterered ./a.sh /dev/vg/lvol0 Do you wish to use the existing LVMy DM ioctl returned -1[root@localhost sam] [root@localhost sam]# ./ohsm -l /dev/sda7 option l +4096512 Physical volume "/dev/sda7" successfully created Volume group "vg" successfully created Rounding up size to full physical extent 1.95 GB Logical volume "lvol0" created Logical volume Physical volume and Volume group created This ioctl gives the information about the logical volume and devices beneath DM ioctl returned -1[root@localhost sam]#
Jan 31, 2009
Why is this IOCTL return -1 ? I know the reason but kindly correct your printf. Rohit, Can you list all the options that OHSM 1.0.0 supports and the parameters it takes. Also mention its use. Now @ your logs. On a real system. I dont want these messages like. 1. Whats this number +4096512? ?? 2. This ioctl gives the information .....??? 3. option l ???? 4 for -u option why are you displaying the LV name in the output... Either change it or justify it ??? I dont like them.
Status:
In-progress
Cc: -fscops -sandeepksinha -imreckless -postrishi -sneha.hendre -checkout.vineet -bharati.alatgi Labels: -Priority-Critical Priority-High
Feb 1, 2009
@log [root@localhost sam]# ./ohsm -f /dev/ohsm_vg/lvol0 Logical Volume and their devices /dev/ohsm_vg/lvol0 /dev/sda7 /dev/sda6 [root@localhost sam]# ./ohsm -u /dev/ohsm_vg/lvol0 DM ioctl returned Success [root@localhost sam]# ./ohsm -l /dev/sda7 /dev/sda6 Creates LVM by specifying the devives Physical volume "/dev/sda7" successfully created Physical volume "/dev/sda6" successfully created Volume group "ohsm_vg" successfully created Rounding up size to full physical extent 18.55 GB Logical volume "lvol0" created Logical volume Physical volume and Volume group created DM ioctl returned Success
Feb 1, 2009
The final options that OHSM 1.0.0 supports will be uploaded asap.
Feb 1, 2009
>>> [root@localhost sam]# ./ohsm -u /dev/ohsm_vg/lvol0 >> DM ioctl returned Success This is also called by default as well, when ever you enable OHSM. Rishi you also verify this from the code. Meaning if someone enables OHSM, he should not need to use this ioctl separately. You should call the ioctl internally in the code for "-e".
Feb 1, 2009
We anre sending ioctl to DM ONLY in the option " -e " as there is no need of the mapper table if ohsm is not enabled
Feb 2, 2009
I have modified the scripts for my use RV good work close the issue if possible
Feb 3, 2009
Closing the issue as the user space code is freezed
Summary:
IOCTL interface
Status: Fixed Labels: -Priority-High Priority-Critical |