[digikam] [Bug 317714] New: Consider working on NFS shares a legitimate use case (even for the targeted home environment)

[Holger Steinhaus]

https://bugs.kde.org/show_bug.cgi?id=317714

            Bug ID: 317714
           Summary: Consider working on NFS shares a legitimate use case
                    (even for the targeted home environment)
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: [hidden email]
          Reporter: [hidden email]

The first-run assistant advises not to store the metadata db on a network
share. This is a very dangerous advice in environments, where all user data is
normally kept on network shares and local drives are not subject to backup
(like in my home environment employing a central NAS device).

Reproducible: Always

Steps to Reproduce:
n/a

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=317714

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
          Component|general                     |Database

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=317714

Marcel Wiesweg <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |UPSTREAM

--- Comment #1 from Marcel Wiesweg <[hidden email]> ---
This is not something in our scope to fix for SQLite,
Please read http://www.sqlite.org/atomiccommit.html section 9.1 for further
information.
Of course, MySQL will not be affected.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rex Dieter]

https://bugs.kde.org/show_bug.cgi?id=317714

Rex Dieter <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #2 from Rex Dieter <[hidden email]> ---
This?

"We have received reports of implementations of both Windows network
filesystems and NFS in which locking was subtly broken. We can not verify these
reports, but as locking is difficult to get right on a network filesystem we
have no reason to doubt them. You are advised to avoid using SQLite on a
network filesystem in the first place, since performance will be slow. But if
you must use a network filesystem to store SQLite database files, consider
using a secondary locking mechanism to prevent simultaneous writes to the same
database even if the native filesystem locking mechanism malfunctions."

doesn't exactly say it can't work, just that it's unreliable in some nfs
implementations.  am I missing something?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=317714

--- Comment #3 from Marcel Wiesweg <[hidden email]> ---
Yes, it's possible that it works, but I dont know really and cannot recommend.
I believe the message was much more strict some years ago.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=317714

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Media

--
You are receiving this mail because:
You are the assignee for the bug.