krzf83@gmail.com
2011-Apr-05 23:12 UTC
files on not mounted subvolumes - mysql complains read only
When I''ve used btrfs subvolume, without separately mouting it, for mysql database dir I''ve got Fatal error: Can''t open and lock privilege tables: Table ''host'' is read only when starting mysql. When I''ve put mysql database dir in root of btrfs, not a subvolume, mysql works fine. I''ve checked file for host table, but I could write to it no problem (on subvolume without mouting). I dont know what could be the problem. I did not check it when mouting a subvolume separately -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Li Zefan
2011-Apr-06 01:31 UTC
Re: files on not mounted subvolumes - mysql complains read only
krzf83@gmail.com wrote:> When I''ve used btrfs subvolume, without separately mouting it, for > mysql database dir I''ve got > Fatal error: Can''t open and lock privilege tables: Table ''host'' is read only > when starting mysql. When I''ve put mysql database dir in root of > btrfs, not a subvolume, mysql works fine. > I''ve checked file for host table, but I could write to it no problem > (on subvolume without mouting). I dont know what could be the problem. > I did not check it when mouting a subvolume separatelyThis has been fixed. You can pull the for-linus branch of the btrfs-unstable tree, or Linus'' linux-2.6, or wait for v2.6.39-rc2 to be announced. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html