Hello
About two weeks ago I sent post titled "Issue with dm snapshots" to this
mailing list. I'd like to provide more information about the problem.
Maybe it will help in recognizing the problem.
I tried to find out which is the last git commit after 2.6.28 which with
this script works good. I used git bisect to do this and here is what
I've got:
# git bisect good
fcccf502540e3d752d33b2d8e976034dee81f9f7 is first bad commit
commit fcccf502540e3d752d33b2d8e976034dee81f9f7
Author: Takashi Sato <t-sato@xxxxxxxxxxxxx>
Date: Fri Jan 9 16:40:59 2009 -0800
filesystem freeze: implement generic freeze feature
The ioctls for the generic freeze feature are below.
o Freeze the filesystem
int ioctl(int fd, int FIFREEZE, arg)
fd: The file descriptor of the mountpoint
FIFREEZE: request code for the freeze
arg: Ignored
Return value: 0 if the operation succeeds. Otherwise, -1
o Unfreeze the filesystem
int ioctl(int fd, int FITHAW, arg)
fd: The file descriptor of the mountpoint
FITHAW: request code for unfreeze
arg: Ignored
Return value: 0 if the operation succeeds. Otherwise, -1
Error number: If the filesystem has already been unfrozen,
errno is set to EINVAL.
[akpm@xxxxxxxxxxxxxxxxxxxx: fix CONFIG_BLOCK=n]
Signed-off-by: (...)
:040000 040000 23e26d18d2b4d6be7fb25e9093531e34450e3067
ae47c7559a4f9ff5a98dbaf812d003b9fcd5f46d M fs
:040000 040000 1ca8e10e69d2d4c124b43f2a46c208a96e6c6c82
21d3f4d7ca305612510eb5e3552c3751ebd75644 M include
---------------------
Seems like the last "good" commit was
c4be0c1dc4cdc37b175579be1460f15ac6495e9a - and the first bad is
fcccf502540e3d752d33b2d8e976034dee81f9f7.
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
