lvm2.git - Andy Grover's LVM tree

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add a couple new functions to gdbinit file and decode a couple lv->status flags	Jonathan Earl Brassow	2012-04-10	1	-2/+51
\| \| \| \| \| \|	New functions: - seg_pvs: Print a list of PVs in a seg_pvs list - pv_dev_name: print name of a PV
*	New handy gdb debugging function, "dm_list_size"	Jonathan Earl Brassow	2011-09-28	1	-2/+21
\| \| \| \| \| \|	Example: (gdb) dm_list_size &split_images 1 list items
*	reorder some status flag printing in gdbinit file.	Jonathan Earl Brassow	2011-09-13	1	-15/+15
\|
*	Adjust gdbinit script to new RAID status flag values.	Jonathan Earl Brassow	2011-09-08	1	-8/+8
\|
*	Updates to gdbinit file	Jonathan Earl Brassow	2011-09-01	1	-28/+34
\| \| \| \| \|	1) Add more status flags for printing 2) Fix bug in lv_status_r processing for mirror segment type
*	RAID updates for gdbinit file	Jonathan Earl Brassow	2011-07-01	1	-33/+106
\|
*	gdbinit update	Jonathan Earl Brassow	2011-03-29	1	-0/+8
\| \| \| \| \|	When doing lv_status_r on a sub_lv, do not climb the tree up past the starting point.
*	Watch out for collisions in GDB global namespace.	Jonathan Earl Brassow	2011-03-14	1	-23/+65
\| \| \| \|	Better 'lv_status_r' printing.
*	lv_status_r now prints out status of attached log LVs	Jonathan Earl Brassow	2011-03-11	1	-3/+8
\| \| \| \|	(Print layout could be nicer... :(
*	lv_status_r has been fixed-up so that it supports infinite LV stacking	Jonathan Earl Brassow	2011-03-11	1	-74/+180
\| \| \| \|	(It does not yet follow 'log_lv' or 'origin' links.)
*	detect RAID* LV and segment flags.	Jonathan Earl Brassow	2011-03-11	1	-6/+19
\|
*	gdbinit - A GDB init file to help while debugging LVM.	Jonathan Earl Brassow	2011-03-10	1	-0/+303
	Copy this file as '.gdbinit' to your home directory or your working directory. It adds the following commands to gdb: - first_seg - lv_status - lv_status_r - lv_is_mirrored - seg_item - seg_status - segs_using_this_lv You can get a list of these user-defined commands by typing: (gdb) help user-defined You can get more information on each command by typing: (gdb) help <command>