| To: | nscott@xxxxxxxxxx |
|---|---|
| Subject: | Re: [REVIEW] Don't make lazy counters default for mkfs |
| From: | Donald Douwsma <donaldd@xxxxxxx> |
| Date: | Mon, 03 Mar 2008 11:18:54 +1100 |
| Cc: | Russell Cattelan <cattelan@xxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, Barry Naujok <bnaujok@xxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| In-reply-to: | <1204500895.10190.3.camel@xxxxxxxxxxxxxxxxx> |
| References: | <op.t67mtawg3jf8g2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1204166101.13569.102.camel@xxxxxxxxxxxxxxxxx> <47C87775.2010007@xxxxxxxxxxx> <47C89137.3070805@xxxxxxxxxxx> <47C89303.7070902@xxxxxxxxxxx> <1204500895.10190.3.camel@xxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.6 (X11/20071022) |
Nathan Scott wrote: > On Fri, 2008-02-29 at 17:19 -0600, Russell Cattelan wrote: >>> I thought about that; xfs *could* stick someting in /proc/fs/xfs >> with >>> supported features or somesuch. >>> >>> But, the kernel you mkfs under isn't necessarily the one you're >> going to >>> need to fall back to tomorrow, though... >>> >>> >> True but at least it could make a bit of a intelligent decision. >> and maybe a warning for a while about potentially incompatible flags. > > Might also be a good idea to require -f to force a mkfs of a filesystem > which the kernel doesn't support. Could work but I dont like the idea of using -f for anything but mkfsing an existing filesystem. If that becomes habit for people it could lead to disasters. Don |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [REVIEW] Don't make lazy counters default for mkfs, Timothy Shimmin |
|---|---|
| Next by Date: | Re: [REVIEW] Don't make lazy counters default for mkfs, Nathan Scott |
| Previous by Thread: | Re: [REVIEW] Don't make lazy counters default for mkfs, Niv Sardi |
| Next by Thread: | Re: [REVIEW] Don't make lazy counters default for mkfs, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |