From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: [PATCH v16 00/22] Richacls (Core and Ext4)
Date: Thu, 3 Dec 2015 17:24:33 -0600 [thread overview]
Message-ID: <5660CF31.1000101@sandeen.net> (raw)
In-Reply-To: <1449090088-9281-1-git-send-email-agruenba@redhat.com>
(try again, replying to list this time, doh!)
On 12/3/15 12:48 PM, Reinoud Koornstra wrote:
> Hi Everyone,
>
> Periodically I seem to have some issues with xfs on my SSD.
> smartd reports this:
>
> Device: /dev/sdb [SAT], Crucial_CT256M550SSD3, S/N:15020ED48DF8,
> WWN:5-00a075-10ed48df8, FW:MU02, 256 GB
>
> reinoud@Mipam:~$ uname -a
> Linux Mipam 4.1.10-custom #1 SMP Tue Oct 20 11:20:40 MDT 2015 x86_64
> x86_64 x86_64 GNU/Linux
>
> The distro is ubuntu 14.04
> reinoud@Mipam:~$ xfs_repair -V
> xfs_repair version 3.2.3
>
> I am not sure if I have any errors, but I did get problems building
> some stuff after a simple hg clone or git clone that others aren't
> seeing.
Missing build dependencies maybe? What problems?
> Earlier I did disable the write cache back.
> I just did run an xfs_repair:
>
> reinoud@Mipam:~$ sudo xfs_repair -v /dev/sdb1
> Phase 1 - find and verify superblock...
> - block cache size set to 1515280 entries
> Phase 2 - using internal log
> - zero log...
> zero_log: head block 26744 tail block 26744
> - scan filesystem freespace and inode maps...
> - found root inode chunk
> Phase 3 - for each AG...
> - scan and clear agi unlinked lists...
> - process known inodes and perform inode discovery...
> - agno = 0
> - agno = 1
> - agno = 2
> - agno = 3
> - process newly discovered inodes...
> Phase 4 - check for duplicate blocks...
> - setting up duplicate extent list...
> - check for inodes claiming duplicate blocks...
> - agno = 0
> - agno = 1
> - agno = 2
> - agno = 3
> Phase 5 - rebuild AG headers and trees...
> - agno = 0
> - agno = 1
> - agno = 2
> - agno = 3
> - reset superblock...
> Phase 6 - check inode connectivity...
> - resetting contents of realtime bitmap and summary inodes
> - traversing filesystem ...
> - agno = 0
> - agno = 1
> - agno = 2
> - agno = 3
> - traversal finished ...
> - moving disconnected inodes to lost+found ...
> Phase 7 - verify and correct link counts...
>
> XFS_REPAIR Summary Thu Dec 3 11:37:01 2015
>
> Phase Start End Duration
> Phase 1: 12/03 11:36:21 12/03 11:36:21
> Phase 2: 12/03 11:36:21 12/03 11:36:27 6 seconds
> Phase 3: 12/03 11:36:27 12/03 11:36:55 28 seconds
> Phase 4: 12/03 11:36:55 12/03 11:36:58 3 seconds
> Phase 5: 12/03 11:36:58 12/03 11:36:58
> Phase 6: 12/03 11:36:58 12/03 11:37:01 3 seconds
> Phase 7: 12/03 11:37:01 12/03 11:37:01
>
> Total run time: 40 seconds
> done
> Did I have errors? I saw disconnected inodes, but other than that.....
No, that was a clean repair run.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-12-03 23:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 21:01 [PATCH v16 00/22] Richacls (Core and Ext4) Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 01/22] vfs: Add IS_ACL() and IS_RICHACL() tests Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 02/22] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 03/22] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD " Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 04/22] vfs: Make the inode passed to inode_change_ok non-const Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 05/22] vfs: Add permission flags for setting file attributes Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 06/22] richacl: In-memory representation and helper functions Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 07/22] richacl: Permission mapping functions Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 08/22] richacl: Compute maximum file masks from an acl Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 09/22] richacl: Permission check algorithm Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 10/22] posix_acl: Unexport acl_by_type and make it static Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 11/22] vfs: Cache base_acl objects in inodes Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 12/22] vfs: Add get_richacl and set_richacl inode operations Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 13/22] vfs: Cache richacl in struct inode Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 14/22] richacl: Update the file masks in chmod() Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 15/22] richacl: Check if an acl is equivalent to a file mode Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 16/22] richacl: Create-time inheritance Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 17/22] richacl: Automatic Inheritance Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 18/22] richacl: xattr mapping functions Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 19/22] richacl: Add richacl xattr handler Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 20/22] vfs: Add richacl permission checking Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 21/22] ext4: Add richacl support Andreas Gruenbacher
2015-12-02 21:01 ` [PATCH v16 22/22] ext4: Add richacl feature flag Andreas Gruenbacher
2015-12-03 22:17 ` [PATCH v16 00/22] Richacls (Core and Ext4) Andreas Gruenbacher
2015-12-03 23:24 ` Eric Sandeen [this message]
2015-12-04 1:30 ` Eric Sandeen
2015-12-15 11:12 ` Andreas Gruenbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5660CF31.1000101@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox