| commit | 5bb76af1e089ac186c15c6aa792340d22b63d4b4 | |
| author | Robert S Peterson <rpeterso@redhat.com> | |
| Fri, 5 May 2006 20:29:50 +0000 (5 16:29 -0400) | ||
| committer | Steven Whitehouse <swhiteho@redhat.com> | |
| Fri, 5 May 2006 20:29:50 +0000 (5 16:29 -0400) | ||
| tree | 3568b59476b8f9df444164005cdf04b9ce7c231b | treesnapshot (tar.gz zip) |
| parent | 97a35d1e5fab9ff8de27814082b78b2fc9ad94f0 | commitdiff |
[GFS2] Set d_ops for root inode
Well, I managed to track down the bug in gfs2 that was causing
my grief. Below is a patch for the problem. Please incorporate
as you see fit. Or should I say: as you see git.
The problem was basically that you never set d_ops for the root
inode, so the wrong hash algorithm was being used. But only for
the root directory. Turns out that if I used subdirectories, it
used the proper hash and my files were found just fine.
Signed-off-by: Robert S Peterson <rpeterso@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Well, I managed to track down the bug in gfs2 that was causing
my grief. Below is a patch for the problem. Please incorporate
as you see fit. Or should I say: as you see git.
The problem was basically that you never set d_ops for the root
inode, so the wrong hash algorithm was being used. But only for
the root directory. Turns out that if I used subdirectories, it
used the proper hash and my files were found just fine.
Signed-off-by: Robert S Peterson <rpeterso@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
| fs/gfs2/ops_fstype.c | diffblobblamehistory |