Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1365512
| From | Markus Trippelsdorf <markus@trippelsdorf.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: btrfs_destroy_inode WARN_ON. |
| Date | 2016-03-28 16:20 +0200 |
| Message-ID | <rhGbo-8g9-3@gated-at.bofh.it> (permalink) |
| References | <rgmoq-WW-37@gated-at.bofh.it> <rgvi2-7qm-5@gated-at.bofh.it> <rhG1I-8cQ-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2016.03.28 at 10:05 -0400, Josef Bacik wrote: > >Mar 24 10:37:27 x4 kernel: WARNING: CPU: 3 PID: 11838 at fs/btrfs/inode.c:9261 btrfs_destroy_inode+0x22b/0x2a0 > > I saw this running some xfstests on our internal kernels but haven't been > able to reproduce it on my latest enospc work (which is obviously perfect). > What were you doing when you tripped this? I'd like to see if I actually > did fix it or if I still need to run it down. Thanks, I cannot really tell. Looking at the backtrace, both Dave and I were running rm. This warning happened just once on my machine, so the issue is obviously very hard to trigger. -- Markus
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
btrfs_destroy_inode WARN_ON. Dave Jones <davej@codemonkey.org.uk> - 2016-03-25 00:00 +0100
Re: btrfs_destroy_inode WARN_ON. Markus Trippelsdorf <markus@trippelsdorf.de> - 2016-03-25 09:30 +0100
Re: btrfs_destroy_inode WARN_ON. Josef Bacik <jbacik@fb.com> - 2016-03-28 16:10 +0200
Re: btrfs_destroy_inode WARN_ON. Markus Trippelsdorf <markus@trippelsdorf.de> - 2016-03-28 16:20 +0200
Re: btrfs_destroy_inode WARN_ON. Dave Jones <davej@codemonkey.org.uk> - 2016-03-28 03:20 +0200
Re: btrfs_destroy_inode WARN_ON. Dave Jones <davej@codemonkey.org.uk> - 2016-04-01 20:20 +0200
Re: btrfs_destroy_inode WARN_ON. Dave Jones <davej@codemonkey.org.uk> - 2016-04-01 20:20 +0200
csiph-web