Adam Borowski posted on Wed, 19 Apr 2017 23:07:45 +0200 as excerpted: > Too many people come complaining about losing their data -- and indeed, > there's no warning outside a wiki and the mailing list tribal knowledge. > Message severity chosen for consistency with XFS -- "alert" makes dmesg > produce nice red background which should get the point across.
Commenting on the idea and comment, because as a non-coder list regular, that's what I can evaluate fairly. =:^) A kernel dmesg warning like this makes more sense to me than trying to put it in, for instance, mkfs.btrfs, because the instability is primarily kernel code and at least the message can stay synced with it, being removed when considered appropriate, unlike userspace code which can't, because people often run userspace and kernelspace versions well out of sync with each other. > I intend to ask for inclusion of this one (or an equivalent) in 4.9, > either in Debian or via GregKH -- while for us kernels "that old" are > history, regular users expect stable releases to be free of known > serious data loss bugs. Arguably it should go in the LTS-4.4 series as well, because we at least try to support the last two LTS series on-list, more or less giving up beyond that, and that's the relatively new 4.9 and the now going stale but we really should be still trying to support it 4.4. Older than that, 4.1 was the only LTS after initial code completion, but since it should be simple enough even before that and certainly would be true, queuing the patch for any still being updated LTS back to initial partial support (3.9 IIRC) is arguably worthwhile. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
