* [Cluster-devel] cluster/gfs-kernel/src/gfs ops_fstype.c
@ 2006-08-10 14:52 rpeterso
0 siblings, 0 replies; 6+ messages in thread
From: rpeterso @ 2006-08-10 14:52 UTC (permalink / raw)
To: cluster-devel.redhat.com
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2006-08-10 14:52:20
Modified files:
gfs-kernel/src/gfs: ops_fstype.c
Log message:
Mounting was mistakenly allowed with too few journals.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&r1=1.26&r2=1.27
--- cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/07/18 20:48:20 1.26
+++ cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/08/10 14:52:20 1.27
@@ -658,7 +658,9 @@
goto fail_sb;
}
- init_journal(sdp, DO);
+ error = init_journal(sdp, DO);
+ if (error)
+ goto fail_sb;
/* Get a handle on the rename lock */
error = gfs_glock_get(sdp, GFS_RENAME_LOCK, &gfs_nondisk_glops,
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Cluster-devel] cluster/gfs-kernel/src/gfs ops_fstype.c
@ 2006-12-19 20:06 teigland
0 siblings, 0 replies; 6+ messages in thread
From: teigland @ 2006-12-19 20:06 UTC (permalink / raw)
To: cluster-devel.redhat.com
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: teigland at sourceware.org 2006-12-19 20:06:44
Modified files:
gfs-kernel/src/gfs: ops_fstype.c
Log message:
When the first mounter is recovering all the journals, it should use
TRY on the journal locks. There's one rare case where other mounters
will exist who hold journal locks that we don't want to block on. That's
when the other mounters are readonly, haven't been able to recover the
fs after a node failure, and the next rw mounter is told to do first
mounter recovery. The journals of these readonly nodes can be skipped
when the pseudo-first mounter is going through all journals. Changed
this a long time ago but never checked it in.
bz 218551
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&r1=1.28&r2=1.29
--- cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/10/23 20:15:28 1.28
+++ cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/12/19 20:06:44 1.29
@@ -436,7 +436,7 @@
for (x = 0; x < sdp->sd_journals; x++) {
error = gfs_recover_journal(sdp,
x, sdp->sd_jindex + x,
- TRUE);
+ FALSE);
if (error) {
printk("GFS: fsid=%s: error recovering journal %u: %d\n",
sdp->sd_fsname, x, error);
^ permalink raw reply [flat|nested] 6+ messages in thread* [Cluster-devel] cluster/gfs-kernel/src/gfs ops_fstype.c
@ 2006-12-19 20:07 teigland
0 siblings, 0 replies; 6+ messages in thread
From: teigland @ 2006-12-19 20:07 UTC (permalink / raw)
To: cluster-devel.redhat.com
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: teigland at sourceware.org 2006-12-19 20:07:26
Modified files:
gfs-kernel/src/gfs: ops_fstype.c
Log message:
When the first mounter is recovering all the journals, it should use
TRY on the journal locks. There's one rare case where other mounters
will exist who hold journal locks that we don't want to block on. That's
when the other mounters are readonly, haven't been able to recover the
fs after a node failure, and the next rw mounter is told to do first
mounter recovery. The journals of these readonly nodes can be skipped
when the pseudo-first mounter is going through all journals. Changed
this a long time ago but never checked it in.
bz 218551
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.28&r2=1.28.2.1
--- cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/10/23 20:15:28 1.28
+++ cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/12/19 20:07:25 1.28.2.1
@@ -436,7 +436,7 @@
for (x = 0; x < sdp->sd_journals; x++) {
error = gfs_recover_journal(sdp,
x, sdp->sd_jindex + x,
- TRUE);
+ FALSE);
if (error) {
printk("GFS: fsid=%s: error recovering journal %u: %d\n",
sdp->sd_fsname, x, error);
^ permalink raw reply [flat|nested] 6+ messages in thread* [Cluster-devel] cluster/gfs-kernel/src/gfs ops_fstype.c
@ 2006-12-19 20:07 teigland
0 siblings, 0 replies; 6+ messages in thread
From: teigland @ 2006-12-19 20:07 UTC (permalink / raw)
To: cluster-devel.redhat.com
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL50
Changes by: teigland at sourceware.org 2006-12-19 20:07:45
Modified files:
gfs-kernel/src/gfs: ops_fstype.c
Log message:
When the first mounter is recovering all the journals, it should use
TRY on the journal locks. There's one rare case where other mounters
will exist who hold journal locks that we don't want to block on. That's
when the other mounters are readonly, haven't been able to recover the
fs after a node failure, and the next rw mounter is told to do first
mounter recovery. The journals of these readonly nodes can be skipped
when the pseudo-first mounter is going through all journals. Changed
this a long time ago but never checked it in.
bz 218551
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&only_with_tag=RHEL50&r1=1.28&r2=1.28.4.1
--- cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/10/23 20:15:28 1.28
+++ cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/12/19 20:07:45 1.28.4.1
@@ -436,7 +436,7 @@
for (x = 0; x < sdp->sd_journals; x++) {
error = gfs_recover_journal(sdp,
x, sdp->sd_jindex + x,
- TRUE);
+ FALSE);
if (error) {
printk("GFS: fsid=%s: error recovering journal %u: %d\n",
sdp->sd_fsname, x, error);
^ permalink raw reply [flat|nested] 6+ messages in thread* [Cluster-devel] cluster/gfs-kernel/src/gfs ops_fstype.c
@ 2007-06-19 14:23 rpeterso
0 siblings, 0 replies; 6+ messages in thread
From: rpeterso @ 2007-06-19 14:23 UTC (permalink / raw)
To: cluster-devel.redhat.com
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2007-06-19 14:23:29
Modified files:
gfs-kernel/src/gfs: ops_fstype.c
Log message:
Resolves: bz 240570: Can't mount GFS file system on AoE device
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&r1=1.30&r2=1.31
--- cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/12/21 20:50:43 1.30
+++ cluster/gfs-kernel/src/gfs/ops_fstype.c 2007/06/19 14:23:29 1.31
@@ -178,6 +178,9 @@
snprintf(sdp->sd_proto_name, 256, "%s", proto);
snprintf(sdp->sd_table_name, 256, "%s", table);
+ while ((table = strchr(sdp->sd_table_name, '/')))
+ *table = '_';
+
out:
kfree(sb);
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Cluster-devel] cluster/gfs-kernel/src/gfs ops_fstype.c
@ 2007-06-19 14:25 rpeterso
0 siblings, 0 replies; 6+ messages in thread
From: rpeterso @ 2007-06-19 14:25 UTC (permalink / raw)
To: cluster-devel.redhat.com
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: rpeterso at sourceware.org 2007-06-19 14:25:04
Modified files:
gfs-kernel/src/gfs: ops_fstype.c
Log message:
Resolves: bz 240570: Can't mount GFS file system on AoE device
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.28.2.2&r2=1.28.2.3
--- cluster/gfs-kernel/src/gfs/ops_fstype.c 2006/12/21 20:55:24 1.28.2.2
+++ cluster/gfs-kernel/src/gfs/ops_fstype.c 2007/06/19 14:25:04 1.28.2.3
@@ -178,6 +178,9 @@
snprintf(sdp->sd_proto_name, 256, "%s", proto);
snprintf(sdp->sd_table_name, 256, "%s", table);
+ while ((table = strchr(sdp->sd_table_name, '/')))
+ *table = '_';
+
out:
kfree(sb);
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-06-19 14:25 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-10 14:52 [Cluster-devel] cluster/gfs-kernel/src/gfs ops_fstype.c rpeterso
-- strict thread matches above, loose matches on Subject: below --
2006-12-19 20:06 teigland
2006-12-19 20:07 teigland
2006-12-19 20:07 teigland
2007-06-19 14:23 rpeterso
2007-06-19 14:25 rpeterso
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.