[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#838607: marked as done (linux-image-4.7.0-0.bpo.1-amd64-unsigned: new file date writing issue)

Your message dated Thu, 22 Dec 2016 00:05:24 +0000
with message-id <1482365124.2677.7.camel@decadent.org.uk>
and subject line Re: Bug#838607: linux-image-4.7.0-0.bpo.1-amd64-unsigned: new file date writing issue
has caused the Debian Bug report #838607,
regarding linux-image-4.7.0-0.bpo.1-amd64-unsigned: new file date writing issue
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
838607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838607
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-4.7.0-0.bpo.1-amd64-unsigned
Version: 4.7.2-1~bpo8+1
Severity: normal
There's a bug with ext4 on the new 4.7 kernel -- rare but it happened here on an ext4 mountpoint (/home /dev/md1 ext4 rw,relatime,data=ordered)
when a new file is created, the "create time" is not properly set.(2014 was written as the create year instead of 2016)
it occured today after I updated to 4.7 so I can only assume it has something to do with it..
my system here has "mdadm" containers, and perhaps it's possible a set of conditions allowed this rarity to occur.
--- End Message ---
--- Begin Message --- 
Closing due to lack of response.

Ben.

-- 
Ben Hutchings
Man invented language to satisfy his deep need to complain. - Lily
Tomlin

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: