<div dir="ltr"><div class="gmail_default" style="font-family:'trebuchet ms',sans-serif;font-size:small;color:rgb(0,0,153)"><span style="font-family:arial;color:rgb(34,34,34)">On Fri, Aug 9, 2013 at 6:52 PM, Joshua C. </span><span dir="ltr" style="font-family:arial;color:rgb(34,34,34)"><<a href="mailto:joshuacov@gmail.com" target="_blank">joshuacov@gmail.com</a>></span><span style="font-family:arial;color:rgb(34,34,34)"> wrote:</span><br>
</div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">
<div class="h5">2013/8/9 Joshua C. <<a href="mailto:joshuacov@gmail.com">joshuacov@gmail.com</a>>:<br>
> 2013/8/9 Joshua C. <<a href="mailto:joshuacov@gmail.com">joshuacov@gmail.com</a>>:<br>
>> 2013/8/9 Frederick Grose <<a href="mailto:fgrose@gmail.com">fgrose@gmail.com</a>>:<br>
>>> On Thu, Aug 8, 2013 at 6:15 PM, Joshua C. <<a href="mailto:joshuacov@gmail.com">joshuacov@gmail.com</a>> wrote:<br>
>>>><br>
>>>> My raid1 gets corrupted _everytime_ I shut down a<br>
>>>> f19-kde-livecd-image. I used kernel.f19 and mdadm.f19 in a f17-livecd<br>
>>>> and everything works fine. So these two are not the problem.<br>
>>>><br>
>>>> What should I look at? maybe dracut???<br>
>>>><br>
>>>> PS: Testing and experimenting isn't a good idea here because it takes<br>
>>>> almost 3 hours for the raid to rebuild...<br>
>>>><br>
>>>> --<br>
>>>> --joshua<br>
>>><br>
>>><br>
>>> With Fedora-Live-Desktop-x86_64-19-1 installed to a vfat formatted Live USB<br>
>>> device, I find this report in /var/log/messages on each reboot:<br>
>>><br>
>>> Aug 8 17:24:09 localhost kernel: [ 8.255350] FAT-fs (sdc1): Volume was<br>
>>> not properly unmounted. Some data may be corrupt. Please run fsck.<br>
>>> Aug 8 17:24:09 localhost kernel: [ 11.052845] bio: create slab <bio-1> at<br>
>>> 1<br>
>>> Aug 8 17:24:09 localhost kernel: [ 11.179108] EXT4-fs (dm-0): mounted<br>
>>> filesystem with ordered data mode. Opts: (null)<br>
>>><br>
>>> Once unmounted, fsck reports that the dirty bit is set:<br>
>>><br>
>>> [root@localhost ~]# fsck.vfat -rv /dev/sdc1<br>
>>> fsck.fat 3.0.22 (2013-07-19)<br>
>>> fsck.fat 3.0.22 (2013-07-19)<br>
>>> Checking we can access the last sector of the filesystem<br>
>>> 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be<br>
>>> corrupt.<br>
>>> 1) Remove dirty bit<br>
>>> 2) No action<br>
>>> ? 1<br>
>>> Boot sector contents:<br>
>>> System ID "SYSLINUX"<br>
>>> Media byte 0xf8 (hard disk)<br>
>>> 512 bytes per logical sector<br>
>>> 4096 bytes per cluster<br>
>>> 32 reserved sectors<br>
>>> First FAT starts at byte 16384 (sector 32)<br>
>>> 2 FATs, 32 bit entries<br>
>>> 7798784 bytes per FAT (= 15232 sectors)<br>
>>> Root directory start at cluster 2 (arbitrary size)<br>
>>> Data area starts at byte 15613952 (sector 30496)<br>
>>> 1948715 data clusters (7981936640 bytes)<br>
>>> 62 sectors/track, 247 heads<br>
>>> 0 hidden sectors<br>
>>> 15620218 sectors total<br>
>>> Checking for unused clusters.<br>
>>> Checking free cluster summary.<br>
>>> Perform changes ? (y/n) y<br>
>>> /dev/sdc1: 18 files, 644955/1948715 clusters<br>
>>><br>
>>> I wonder if this may be due to a Bash shell not getting properly shut down<br>
>>> during shutdown, as reported here,<br>
>>> <a href="http://lists.freedesktop.org/archives/systemd-devel/2013-July/012307.html" target="_blank">http://lists.freedesktop.org/archives/systemd-devel/2013-July/012307.html</a><br>
>>><br>
>>> --Fred<br>
>>><br>
>>><br>
>>> --<br>
>>> livecd mailing list<br>
>>> <a href="mailto:livecd@lists.fedoraproject.org">livecd@lists.fedoraproject.org</a><br>
>>> <a href="https://admin.fedoraproject.org/mailman/listinfo/livecd" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/livecd</a><br>
>><br>
>> I was suspecting that systemd could be involved. Do you know if there<br>
>> is a patch about this?<br>
>><br>
>> Since I'm using a livecd image without persistent overlay, there is no<br>
>> way to find any logs from the shutting down process. But this is very<br>
>> frustrating....<br>
>><br>
>><br>
>> --<br>
>> --joshua<br>
><br>
> I'll backport commits 82659fd7571bda0f3dce9755b89a23c411d53dda "core:<br>
> optionally send SIGHUP in addition to the configured kill signal" and<br>
> a6c0353b9268d5b780fb7ff05a10cb5031446e5d "core: open up SendSIGHUP<br>
> property for transient units" to systemd-204 and turn this on in my<br>
> test built. I hope this can fix the problem.<br>
><br>
> As I already said, it annoying to rebuild the raid after every reboot!!!<br>
><br>
> Has this behavior been reported in a real installation (no livecds)?<br>
><br>
><br>
> --<br>
> --joshua<br>
<br>
</div></div>I tested this with systemd<br>
git-f535088ef72a92533f2c4270d06289c89737fa2a "systemctl: add missing<br>
newline to --help output" as of 20130809 without luck. On every<br>
shutdown my raid1 is marked dirty!!!<br>
<div class=""><div class="h5"><br>
--<br>
--joshua</div></div></blockquote><div><br></div><div class="gmail_default" style="font-family:'trebuchet ms',sans-serif;font-size:small;color:rgb(0,0,153)">It seems that dosfstools has become more thorough in checking fat volumes in early 2013.</div>
<div class="gmail_default" style="font-family:'trebuchet ms',sans-serif;font-size:small;color:rgb(0,0,153)"><br></div><div class="gmail_default" style="font-family:'trebuchet ms',sans-serif;font-size:small;color:rgb(0,0,153)">
See these commits,</div><div class="gmail_default"><font color="#000099" face="trebuchet ms, sans-serif"><a href="http://daniel-baumann.ch/gitweb/?p=software/dosfstools.git;a=blob;f=ChangeLog;h=414d1db42b385de0f066daa26fb1dc857d0480e1;hb=HEAD#l643">http://daniel-baumann.ch/gitweb/?p=software/dosfstools.git;a=blob;f=ChangeLog;h=414d1db42b385de0f066daa26fb1dc857d0480e1;hb=HEAD#l643</a></font><br>
</div><div class="gmail_default"><font color="#000099" face="trebuchet ms, sans-serif"><br></font></div><div class="gmail_default"><font color="#000099" face="trebuchet ms, sans-serif"> --Fred</font></div></div></div>
</div>