On 28/09/05, Larry K <[EMAIL PROTECTED]> wrote: > Calling all LVM experts!! > > Up until recently, I had been running LVM with only a single physical > volume. I probably have 100GB of data files in the volume, waiting to be > watched. So, Myth was running fine and all was well, except I had a 150GB > partition just laying around, not in use. So, I decided to extend my volume > group and add this 150GB to it, like so: > > Using fdisk, deleted /dev/hda4 partition > Using fdisk, created /dev/hda4 as LVM > Created physical volume: pvcreate /dev/hda4 > Extended volume group: vgextend vg /dev/hda4 > Ran vgdisplay to see amount of free space that needs to be extended (18214) > unmount the volume group: umount /dev/vg/video > extend: lvextend -l +18214 /dev/vg/video > mount /dev/vg/video > grow the xfs file system: xfs_grow /dev/vg/video > Remove /video from /etc/fstab > Now, df -k shows the new space: > > [EMAIL PROTECTED] ~]# df -k > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/hda2 10080520 2938120 6630332 31% / > /dev/hda1 101086 16752 79115 18% /boot > none 257908 0 257908 0% /dev/shm > /dev/mapper/vg-video 442105856 113816336 328289520 26% /video2 > > Everything appeared to be OK. I now had a 450GB partition for myth, instead > of 300GB. However, I soon discovered that new files are written with a > length of zero (empty files). Doh! The mythfrontend was able to play back > the existing files that were in the VG, but if I tried to delete a file, the > frontend would hang. That's when I knew I had a problem for sure. >
You did use mythtvsetup to tell myth to use /video2 instead of /video, and make sure the permissions were correct, didn't you? _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
