1 |
On Wed, Oct 24, 2012 at 10:51 PM, Kerin Millar <kerframil@×××××××××××.uk>wrote: |
2 |
|
3 |
> Canek Peláez Valdés wrote: |
4 |
> |
5 |
>> On Wed, Oct 24, 2012 at 8:09 PM, Kerin Millar<kerframil@××××××××.co.**uk<kerframil@×××××××××××.uk>> |
6 |
>> wrote: |
7 |
>> |
8 |
>>> Canek Peláez Valdés wrote: |
9 |
>>> |
10 |
>>>> On Wed, Oct 24, 2012 at 8:54 AM, Nikos Chantziaras<realnc@×××××.com> |
11 |
>>>> wrote: |
12 |
>>>> |
13 |
>>>>> Kernels 3.4, 3.5, and 3.6 can result in severe data corruption if |
14 |
>>>>> you're |
15 |
>>>>> using the EXT4 filesystem: |
16 |
>>>>> |
17 |
>>>>> http://www.phoronix.com/scan.**php?page=news_item&px=MTIxNDQ<http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ> |
18 |
>>>>> |
19 |
>>>>> This includes gentoo-sources. I hope the Gentoo developers are on top |
20 |
>>>>> of |
21 |
>>>>> this. In the meantime, avoid doing reboots after too short an uptime. |
22 |
>>>>> |
23 |
>>>> |
24 |
>>>> Doesn't seem to be that serious: |
25 |
>>>> |
26 |
>>>> https://plus.google.com/u/0/**117091380454742934025/posts/**Wcc5tMiCgq7<https://plus.google.com/u/0/117091380454742934025/posts/Wcc5tMiCgq7> |
27 |
>>>> |
28 |
>>> |
29 |
>>> Might I enquire as to the manner in which this comment impartially |
30 |
>>> establishes that the consequences of the bug upon those affected is not |
31 |
>>> serious? |
32 |
>>> |
33 |
>> |
34 |
>> Oh, and about "impartiality"; this is a technical issue, not a |
35 |
>> philosophical one. I will always trust the expert's opinion over |
36 |
>> almost everyone's else. |
37 |
>> |
38 |
>> |
39 |
> The comment you linked to was fairly bereft of technical content, other |
40 |
> than to assert that the circumstances under which the bug triggers are so |
41 |
> limited that there is no general cause for concern. Given that (a) the |
42 |
> investigation chronicled by the lkml thread remains ongoing (b) a remedy |
43 |
> has yet to be conclusively determined, it is illogical that any statement |
44 |
> as to the scope of the bug can anything more than a hypothesis at best, |
45 |
> irrespective of how well-informed said hypothesis might be. |
46 |
> |
47 |
> As for impartiality, it is entirely conceivable that someone in Ted's |
48 |
> position would be riled by what they perceive (not necessarily correctly) |
49 |
> as negative publicity and to respond in kind. Particularly when one carries |
50 |
> a burden of responsibility of the subsystem in question. |
51 |
> |
52 |
> Until such time as the matter is concluded, ext4 users that value their |
53 |
> data will exercise due concern, naturally. The petty sniping about drumming |
54 |
> up ad-revenue and silly 4chan style image memes do not strike me as a |
55 |
> constructive way in which to assuage those concerns. |
56 |
> |
57 |
> Further, the notion that nobarrier is an "esoteric" option is |
58 |
> questionable. In my experience, it is common practice to employ it as a |
59 |
> performance-enhancing measure on systems equipped with a battery-backed |
60 |
> write cache; especially MySQL servers that must contend with a heavy |
61 |
> workload. One wonders what he would have made of the notion of running ext4 |
62 |
> without a journal, had it not been at the behest of Google. |
63 |
> |
64 |
> In summary, I maintain that his fatuous Google+ post does nothing to |
65 |
> establish just why it is that those of us in the peanut gallery should be |
66 |
> unconcerned as to the impact of the bug. On my part, I will continue to be |
67 |
> concerned until the investigation has fully run its course. |
68 |
> |
69 |
> --Kerin |
70 |
> |
71 |
> |
72 |
http://lwn.net/Articles/521022/ |
73 |
|
74 |
Links to relevant analysis. Useful comments. 'nuff said. |
75 |
|
76 |
-- |
77 |
:wq |