summaryrefslogtreecommitdiffstats
path: root/fs/gfs2/recovery.c
diff options
context:
space:
mode:
authorRobert S Peterson <rpeterso@redhat.com>2006-05-05 16:29:50 -0400
committerSteven Whitehouse <swhiteho@redhat.com>2006-05-05 16:29:50 -0400
commit5bb76af1e089ac186c15c6aa792340d22b63d4b4 (patch)
tree3568b59476b8f9df444164005cdf04b9ce7c231b /fs/gfs2/recovery.c
parent97a35d1e5fab9ff8de27814082b78b2fc9ad94f0 (diff)
downloadlinux-5bb76af1e089ac186c15c6aa792340d22b63d4b4.tar.gz
linux-5bb76af1e089ac186c15c6aa792340d22b63d4b4.tar.bz2
linux-5bb76af1e089ac186c15c6aa792340d22b63d4b4.zip
[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>
Diffstat (limited to 'fs/gfs2/recovery.c')
0 files changed, 0 insertions, 0 deletions