Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+xfs_admin\:\s+exit\s+gracefully\s+for\s+non\-XFS\s+fileststems\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+xfs_admin\:\s+exit\s+gracefully\s+for\s+non\-XFS\s+fileststems\s*$/: 3 ]

Total 3 documents matching your query.

1. [PATCH] xfs_admin: exit gracefully for non-XFS fileststems (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Sun, 25 Jan 2009 06:03:42 +0100; Exit gracefully if the magic number doesn't match xfs in xfs_admin and xfs_ncheck. This is implemented by a new -C option to xfs_db which makes it exit with a useful error message in case the filesys; /archives/xfs/2009-01/msg01101.html (11,010 bytes)
2. Re: [PATCH] xfs_admin: exit gracefully for non-XFS fileststems (score: 1): Author: "Josef 'Jeff' Sipek" <jeffpc@xxxxxxxxxxxxxx>; Date: Sun, 25 Jan 2009 00:56:18 -0500; ... ... Obviously, the 'C' is supposed to stand for "check". I think that's misleading. xfs_db _always_ checks the SB magic. This option just changes the the behavior on a mis-match. In a way, I thin; /archives/xfs/2009-01/msg01102.html (8,394 bytes)
3. Re: [PATCH] xfs_admin: exit gracefully for non-XFS fileststems (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Thu, 29 Jan 2009 16:43:38 -0500; I guess I'd rather see this the reverse, and require a flag to allow xfs_db to work on something that doesn't look like xfs - err on the side of safety (hm but I suppose db is usually in read-only mo; /archives/xfs/2009-01/msg01221.html (8,480 bytes)

Current List: 1 - 3
Page: [1]