[digiKam-users] Avoid full rescan if a network collection isn't available?

[AndriusWild]

Hello,

I forgot to run my "mount -t cifs..." command after reboot and started digiKam.

Since the network collection was not available looks like digiKam removed it from the database. I mounted the folder and restarted digiKam but seems like it is re-scanning and re-adding the whole collection now which is going to take few hours.

I am wondering if there is a way to keep network collections in the database despite their current (un)availability.

Any ideas would be appreciated.

[AndriusWild]

Forgot to add:

I am usung the latest digikam 6.3.0 from KDE Neon repo.

On Mon, Oct 21, 2019 at 8:43 AM Andrey Goreev <[hidden email]> wrote:

Hello,

I forgot to run my "mount -t cifs..." command after reboot and started digiKam.

Since the network collection was not available looks like digiKam removed it from the database. I mounted the folder and restarted digiKam but seems like it is re-scanning and re-adding the whole collection now which is going to take few hours.

I am wondering if there is a way to keep network collections in the database despite their current (un)availability.

Any ideas would be appreciated.

Thanks,

Andrey

[Maik Qualmann]

And the collection was/is registered as a network collection in digiKam?
Normally, digiKam would not clean up the database. However, there must be no
folder or file in the mount path, otherwise digiKam assumes that the network
collection is mounted.

Maik

Am Montag, 21. Oktober 2019, 16:43:57 CEST schrieb Andrey Goreev:

> Forgot to add:
> I am usung the latest digikam 6.3.0 from KDE Neon repo.
>
> Thanks,
> Andrey
>
> On Mon, Oct 21, 2019 at 8:43 AM Andrey Goreev <[hidden email]> wrote:
> > Hello,
> >
> > I forgot to run my "mount -t cifs..." command after reboot and started
> > digiKam.
> > Since the network collection was not available looks like digiKam removed
> > it from the database. I mounted the folder and restarted digiKam but seems
> > like it is re-scanning and re-adding the whole collection now which is
> > going to take few hours.
> >
> > I am wondering if there is a way to keep network collections in the
> > database despite their current (un)availability.
> >
> > Any ideas would be appreciated.
> >
> > Thanks,
> > Andrey

[AndriusWild]

For some reason the collection was marked as 'local'. I am not sure how did that happen. I am pretty positive I chose 'network' when was adding it.

I changed the type of the collection to 'network' now and am adding it to the database again. Let's see if that helps.

However,  the NAS is mounted into my /home/user/Pictures directory.

Is it going to be a problem?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Maik Qualmann <[hidden email]>

Date: 2019-10-21 11:37 a.m. (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: [digiKam-users] Avoid full rescan if a network collection isn't available?

And the collection was/is registered as a network collection in digiKam?
Normally, digiKam would not clean up the database. However, there must be no
folder or file in the mount path, otherwise digiKam assumes that the network
collection is mounted.

Maik

Am Montag, 21. Oktober 2019, 16:43:57 CEST schrieb Andrey Goreev:

> Forgot to add:
> I am usung the latest digikam 6.3.0 from KDE Neon repo.
>
> Thanks,
> Andrey
>
> On Mon, Oct 21, 2019 at 8:43 AM Andrey Goreev <[hidden email]> wrote:
> > Hello,
> >
> > I forgot to run my "mount -t cifs..." command after reboot and started
> > digiKam.
> > Since the network collection was not available looks like digiKam removed
> > it from the database. I mounted the folder and restarted digiKam but seems
> > like it is re-scanning and re-adding the whole collection now which is
> > going to take few hours.
> >
> > I am wondering if there is a way to keep network collections in the
> > database despite their current (un)availability.
> >
> > Any ideas would be appreciated.
> >
> > Thanks,
> > Andrey

[Remco Viëtor]

On mardi 22 octobre 2019 02:13:07 CEST Andrey Goreev wrote:
> For some reason the collection was marked as 'local'. I am not sure how did
> that happen. I am pretty positive I chose 'network' when was adding it.I
> changed the type of the collection to 'network' now and am adding it to the
> database again. Let's see if that helps.However,  the NAS is mounted into
> my /home/user/Pictures directory.Is it going to be a problem?

Do you have a local collection there as well? Then that might be a problem.
Also keep in mind Maik's remark about the mount point not being empty.

Remco

Le 22/10/2019 à 02:13, Andrey Goreev a écrit :
> For some reason the collection was marked as 'local'. I am not sure how
> did that happen. I am pretty positive I chose 'network' when was adding it.

some time again (may be some years) removable collections where marked
local at some point.

I dunno if it's still the case, probably not, but don't remember when
the fix was done

jdd


--
http://dodin.org

[Alex Antão]

I don't know if this is related, but....

In my Mac, I have been exporting my photos to my external HD.

I mounted it on /Volumes/FOTOS, and exported a lot os files there.

Configured this directory as a network drive in Digikam and also to watch this for external changes.

Then, I quit Digikam, unplugged the drive and plugged it on my Time Capsule.

Then shared the drive over network and mounted back in my Mac on the same directory: /Volumes/FOTOS

When I started Digikam, it stopped loading on splashscreen and kept this for hours. Never fully loaded.

Then, I forced it to finish, umounted the Volume and loded Digikam again. It loaded with the DB fully loaded, didn't cleaned it and rescanned again.

Then, for one more test, I mount the network drive back again, but Digikam stopped watch the directory for external changes, I added and removed files but digikam didn't see those changes.

---- Ativado Ter, 22 out 2019 03:25:38 -0300 <[hidden email]> escreveu ----

Le 22/10/2019 à 02:13, Andrey Goreev a écrit :
> For some reason the collection was marked as 'local'. I am not sure how
> did that happen. I am pretty positive I chose 'network' when was adding it.

some time again (may be some years) removable collections where marked
local at some point.

I dunno if it's still the case, probably not, but don't remember when
the fix was done

jdd


--
http://dodin.org

[AndriusWild]

No I do not have a local collection on that laptop.

But the folder where I mount my NAS is empty if the NAS is not available...

Is there a better way to connect to SAMBA share on Linux?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Remco Viëtor <[hidden email]>

Date: 2019-10-21 10:55 p.m. (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: [digiKam-users] Avoid full rescan if a network collection isn't available?

On mardi 22 octobre 2019 02:13:07 CEST Andrey Goreev wrote:
> For some reason the collection was marked as 'local'. I am not sure how did
> that happen. I am pretty positive I chose 'network' when was adding it.I
> changed the type of the collection to 'network' now and am adding it to the
> database again. Let's see if that helps.However,  the NAS is mounted into
> my /home/user/Pictures directory.Is it going to be a problem?

Do you have a local collection there as well? Then that might be a problem.
Also keep in mind Maik's remark about the mount point not being empty.

Remco

[AndriusWild]

I don't think digiKam crashed. Network drives are way slower than local ones so it just takes a very long time to scan them.

It took mine 12 to 18 hours to re-add a 500Gb collection yesterday.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Alex Antão <[hidden email]>

Date: 2019-10-22 5:31 a.m. (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: [digiKam-users] Avoid full rescan if a network collection isn't available?

I don't know if this is related, but....

In my Mac, I have been exporting my photos to my external HD.

I mounted it on /Volumes/FOTOS, and exported a lot os files there.

Configured this directory as a network drive in Digikam and also to watch this for external changes.

Then, I quit Digikam, unplugged the drive and plugged it on my Time Capsule.

Then shared the drive over network and mounted back in my Mac on the same directory: /Volumes/FOTOS

When I started Digikam, it stopped loading on splashscreen and kept this for hours. Never fully loaded.

Then, I forced it to finish, umounted the Volume and loded Digikam again. It loaded with the DB fully loaded, didn't cleaned it and rescanned again.

Then, for one more test, I mount the network drive back again, but Digikam stopped watch the directory for external changes, I added and removed files but digikam didn't see those changes.

---- Ativado Ter, 22 out 2019 03:25:38 -0300 <[hidden email]> escreveu ----

Le 22/10/2019 à 02:13, Andrey Goreev a écrit :
> For some reason the collection was marked as 'local'. I am not sure how
> did that happen. I am pretty positive I chose 'network' when was adding it.

some time again (may be some years) removable collections where marked
local at some point.

I dunno if it's still the case, probably not, but don't remember when
the fix was done

jdd


--
http://dodin.org

[AndriusWild]

The scan finished but the collection showed up in digiKam as 'Local' again...

Is that because the path to the collection looks like a path to a local folder (/home/user/...) ?

On Tue, Oct 22, 2019 at 7:18 AM Andrey Goreev <[hidden email]> wrote:

I don't think digiKam crashed. Network drives are way slower than local ones so it just takes a very long time to scan them.

It took mine 12 to 18 hours to re-add a 500Gb collection yesterday.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Alex Antão <[hidden email]>

Date: 2019-10-22 5:31 a.m. (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: [digiKam-users] Avoid full rescan if a network collection isn't available?

I don't know if this is related, but....

In my Mac, I have been exporting my photos to my external HD.

I mounted it on /Volumes/FOTOS, and exported a lot os files there.

Configured this directory as a network drive in Digikam and also to watch this for external changes.

Then, I quit Digikam, unplugged the drive and plugged it on my Time Capsule.

Then shared the drive over network and mounted back in my Mac on the same directory: /Volumes/FOTOS

When I started Digikam, it stopped loading on splashscreen and kept this for hours. Never fully loaded.

Then, I forced it to finish, umounted the Volume and loded Digikam again. It loaded with the DB fully loaded, didn't cleaned it and rescanned again.

Then, for one more test, I mount the network drive back again, but Digikam stopped watch the directory for external changes, I added and removed files but digikam didn't see those changes.

---- Ativado Ter, 22 out 2019 03:25:38 -0300 <[hidden email]> escreveu ----

Le 22/10/2019 à 02:13, Andrey Goreev a écrit :
> For some reason the collection was marked as 'local'. I am not sure how
> did that happen. I am pretty positive I chose 'network' when was adding it.

some time again (may be some years) removable collections where marked
local at some point.

I dunno if it's still the case, probably not, but don't remember when
the fix was done

jdd


--
http://dodin.org

[AndriusWild]

I changed it to 'network' again and looks like it worked this time.

The application crashed once after I checked the box "monitor album for changes" but I did not catch any bug traces unfortunately.

I will see if it works any differently now.

On Tue, Oct 22, 2019 at 7:35 AM Andrey Goreev <[hidden email]> wrote:

The scan finished but the collection showed up in digiKam as 'Local' again...

Is that because the path to the collection looks like a path to a local folder (/home/user/...) ?

Thanks,

Andrey

On Tue, Oct 22, 2019 at 7:18 AM Andrey Goreev <[hidden email]> wrote:

I don't think digiKam crashed. Network drives are way slower than local ones so it just takes a very long time to scan them.

It took mine 12 to 18 hours to re-add a 500Gb collection yesterday.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Alex Antão <[hidden email]>

Date: 2019-10-22 5:31 a.m. (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: [digiKam-users] Avoid full rescan if a network collection isn't available?

I don't know if this is related, but....

In my Mac, I have been exporting my photos to my external HD.

I mounted it on /Volumes/FOTOS, and exported a lot os files there.

Configured this directory as a network drive in Digikam and also to watch this for external changes.

Then, I quit Digikam, unplugged the drive and plugged it on my Time Capsule.

Then shared the drive over network and mounted back in my Mac on the same directory: /Volumes/FOTOS

When I started Digikam, it stopped loading on splashscreen and kept this for hours. Never fully loaded.

Then, I forced it to finish, umounted the Volume and loded Digikam again. It loaded with the DB fully loaded, didn't cleaned it and rescanned again.

Then, for one more test, I mount the network drive back again, but Digikam stopped watch the directory for external changes, I added and removed files but digikam didn't see those changes.

---- Ativado Ter, 22 out 2019 03:25:38 -0300 <[hidden email]> escreveu ----

Le 22/10/2019 à 02:13, Andrey Goreev a écrit :
> For some reason the collection was marked as 'local'. I am not sure how
> did that happen. I am pretty positive I chose 'network' when was adding it.

some time again (may be some years) removable collections where marked
local at some point.

I dunno if it's still the case, probably not, but don't remember when
the fix was done

jdd


--
http://dodin.org