*** This bug is a duplicate of bug 1708096 ***
https://bugs.launchpad.net/bugs/1708096
--- Comment From cha...@us.ibm.com 2018-02-07 13:40 EDT---
I am sorry but I won't be able to investigate this issue any longer and since
there aren't JFS maintainers within the LTC, it is unlikely I
--- Comment From cha...@us.ibm.com 2017-09-25 12:20 EDT---
(In reply to comment #28)
> Apologies but I have not had a chance to revisit this one but will try and
> get to it again next week.
Due to a rather large bug workload and higher priority bugs, I have not
been able to look at this o
--- Comment From cha...@us.ibm.com 2017-05-09 14:58 EDT---
Apologies but I have not had a chance to revisit this one but will try and get
to it again next week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
--- Comment From cha...@us.ibm.com 2017-05-02 08:52 EDT---
Wrote a trial patch that did not release and re-allocate the inode and block
map structures during a remount and jusr re-initialize them as the locking
changes were getting ugly. Still, after several reboots, I still ran into a
s
--- Comment From cha...@us.ibm.com 2017-04-24 18:30 EDT---
The proper IWRITE_LOCK()/IWRITE_UNLOCK() calls around the diUnmount()/diMount()
and similarly racy dbUnmount()/dbMount() may help but not without first
cleaning up code such as:
328 imap = JFS_IP(ipimap)->i_imap;
329 IREA
--- Comment From cha...@us.ibm.com 2017-04-24 17:35 EDT---
Actually, I see examples of taking read locks such as:
2627 /* obtain read lock on map */
2628 IREAD_LOCK(ipimap, RDWRLOCK_IMAP);
2629
2630 /* read the iag */
2631 if ((rc = diIAGRead(imap, iagno, &mp))) {
2632
--- Comment From cha...@us.ibm.com 2017-04-24 17:11 EDT---
In jfs_mount_rw() we have the following:
249 if (remount) {
250 if (chkSuper(sb) || (sbi->state != FM_CLEAN))
251 return -EINVAL;
252
253 truncate_inode_pages(sbi->ipimap->i_mapping, 0);
254
