I just got hit by this, this morning.  Updated SLES12 SP3 and now my XFS
filesystem will not mount.  I truly have no idea how to fix this.  I tried
xfs_repair on the device.  It ran to completion, but I get the same error
when I reboot.
Any suggestions?

Ý  OK  ¨ Found device
/dev/mapper/36005076307ffd4da000000000000003c-part1.

         Starting File System Check on
/dev/...7ffd4da000000000000003c-part1...
Ý  OK  ¨ Started File System Check on
/dev/m...307ffd4da000000000000003c-part1.
         Mounting
/srv/ftp/pub...

SGI XFS with ACLs, security attributes, realtime, no debug
enabled
XFS (dm-4): Mounting V5
Filesystem

XFS (dm-4): Torn write (CRC failure) detected at log block 0x231d3.
Truncating head block from 0x231d7.
XFS (dm-4): failed to locate log
tail
XFS (dm-4): log mount/recovery failed: error
-74
XFS (dm-4): log mount
failed

ÝFAILED¨ Failed to mount
/srv/ftp/pub.

See 'systemctl status srv-ftp-pub.mount' for
details.

On Wed, May 23, 2018 at 7:25 PM, R P Herrold <[email protected]> wrote:

> On Wed, 23 May 2018, Ted Rodriguez-Bell wrote:
>
> > Suse just released a new kernel-default-4.4.131-94.29-1
> > package for SLES 12SP3 with some kernel security fixes.  If
> > you use XFS, don't install it!
>
> My condolences
>
> There has been an (at least) four way finger pointing contest
> raging for the last couple of months (on the Fedoraproject
> front) between:
>         - xfs developers
>         - systemd developers
>         - dracut developers
>         - innocent victims of XFS
>
> Here is a trailhead to read back and forth from:
>         http://tinyurl.com/y7d2a4he
>
> I have a number of Red Hat Bugzilla reports I track, I have
> corresponded twice privately with the Fedoraproject lead about
> applying dynamite to at least get the innocent victims out of
> XFS' harm's way, and ... bupkis.  I have to say the problem
> looks well and truly wedged, and XFS and data I care about
> will never meet
>
> In response, I went into our local deployment SOP's and added
> a general prohibition on using XFS, absent explicit prior
> approval from an admin or greater level authority.  The ONLY
> exception I can see being sought relates to extremely large
> filesystems
>
> -- Russ herrold
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to