Thread (27 messages) 27 messages, 5 authors, 2014-05-06

Re: [PATCH 2/3] mke2fs: print extra information about existing ext2/3/4 file systems

From: Andreas Dilger <hidden>
Date: 2014-05-05 16:25:55
Also in: linux-fsdevel

Note that the MMP block already contains the hostname for informational purposes. 

I'd argue that if you have several hundred SAN attached disks and they are not zoned for specific nodes then using MMP will save your bacon from foolish admins that are trying to use the same disk on multiple nodes. 

Cheers, Andreas
On May 5, 2014, at 8:57, Theodore Ts'o [off-list ref] wrote:
quoted
On Mon, May 05, 2014 at 04:51:25PM +0200, Lukáš Czerner wrote:

Which would be reasonable if there was a consumer of such
information and it seemed to be useful. So I wonder what other
people think about that.

Karel, you had some suggestions about how to utilize that aside from
the mkfs...
Well, if we were going to make this be more general, one other thought
I had was that might be useful to also stash the last hostname in the
superblock.  Consider the situation where you have several hundred
fibre-channel disk volumes in your SAN, and where of course the SAN
administrator hasn't done a good job naming them, and of course the
human sysadmins hadn't bothered to use file system labels.  If we were
automatically stashing the hostname into the superblock at mount time,
it might help in certain cases after the SAN directory gets smashed,
or some such.

                       - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help