On Jan 11, 2014, at 10:10 AM, MegaBrutal <megabru...@gmail.com> wrote:
> 2014/1/11 Hugo Mills <h...@carfax.org.uk>: >> >> It looks like you've shrunk the LV without first shrinking the >> filesystem. Depending on how much you shrunk it by, the odds are >> fairly good that significant chunks of the FS are now toast. >> >> Hugo. >> > > Thank you very much! Strange, I indeed shrinked the LV, but only by a > few megabytes to make space for /boot (as turned out, GRUB2 can't boot > from LVM), GRUB 2.00 (the final release) can definitely boot from LVs, I do it all the time. > and I think I did shrink the FS too... But maybe not. As it > started out as a test system, I intentionally wanted to test some > obscure situations here. Thankfully I don't have considerable data > loss and I don't think any valuable data was on the space that was cut > off. Strange that the system was running like this for a month with > this problem being undetected. Only once the file system needed to write outside of the partition would there likely be an error, but from your dmesg "wr 311347" means several hundred thousand failed write attempts. There are probably other messages similar to this going way back. > > How can I shrink the FS to the correct size right now, ensuring that I > really shrink it to the exact LV size? Right now it's a broken file system, just recreate it. Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
