Get total size of jpeg images per directory in each directory containing jpegs












2















I'm trying to get a per-directory total size of all the .jpg/.jpeg images in each directory that contains such images. And showing the full directory path.



I've managed to cobble this together from various bits I've found.



for i in $(tree -dfi --noreport); do
find . ( -iname "*.jpg" -or -iname "*.jpeg" ) -type f -exec du -c {} ; $i
done


However I'm getting an error:



find: paths must precede expression


Anyone know what I've done wrong?

Or can suggest any alternatives with bash that might do what I'm looking for?



I get the same error when changing it to this:



for i in $(tree -dfi --noreport); do
find $i ( -iname "*.jpg" -or -iname "*.jpeg" ) -type f -exec du {} ; $i
done









share|improve this question




















  • 2





    Is $i the directory where you want to search for jp[e]g images, that is, the path? If so, "[the] path[s] must precede the expression" (the bit where you put the -inames). Why do you have a . after find instead of $i?

    – njsg
    Jan 9 '13 at 16:21













  • Question edited. Still getting the same error.

    – batfastad
    Jan 9 '13 at 17:28






  • 1





    Remove the $i at the end...

    – njsg
    Jan 9 '13 at 17:33
















2















I'm trying to get a per-directory total size of all the .jpg/.jpeg images in each directory that contains such images. And showing the full directory path.



I've managed to cobble this together from various bits I've found.



for i in $(tree -dfi --noreport); do
find . ( -iname "*.jpg" -or -iname "*.jpeg" ) -type f -exec du -c {} ; $i
done


However I'm getting an error:



find: paths must precede expression


Anyone know what I've done wrong?

Or can suggest any alternatives with bash that might do what I'm looking for?



I get the same error when changing it to this:



for i in $(tree -dfi --noreport); do
find $i ( -iname "*.jpg" -or -iname "*.jpeg" ) -type f -exec du {} ; $i
done









share|improve this question




















  • 2





    Is $i the directory where you want to search for jp[e]g images, that is, the path? If so, "[the] path[s] must precede the expression" (the bit where you put the -inames). Why do you have a . after find instead of $i?

    – njsg
    Jan 9 '13 at 16:21













  • Question edited. Still getting the same error.

    – batfastad
    Jan 9 '13 at 17:28






  • 1





    Remove the $i at the end...

    – njsg
    Jan 9 '13 at 17:33














2












2








2








I'm trying to get a per-directory total size of all the .jpg/.jpeg images in each directory that contains such images. And showing the full directory path.



I've managed to cobble this together from various bits I've found.



for i in $(tree -dfi --noreport); do
find . ( -iname "*.jpg" -or -iname "*.jpeg" ) -type f -exec du -c {} ; $i
done


However I'm getting an error:



find: paths must precede expression


Anyone know what I've done wrong?

Or can suggest any alternatives with bash that might do what I'm looking for?



I get the same error when changing it to this:



for i in $(tree -dfi --noreport); do
find $i ( -iname "*.jpg" -or -iname "*.jpeg" ) -type f -exec du {} ; $i
done









share|improve this question
















I'm trying to get a per-directory total size of all the .jpg/.jpeg images in each directory that contains such images. And showing the full directory path.



I've managed to cobble this together from various bits I've found.



for i in $(tree -dfi --noreport); do
find . ( -iname "*.jpg" -or -iname "*.jpeg" ) -type f -exec du -c {} ; $i
done


However I'm getting an error:



find: paths must precede expression


Anyone know what I've done wrong?

Or can suggest any alternatives with bash that might do what I'm looking for?



I get the same error when changing it to this:



for i in $(tree -dfi --noreport); do
find $i ( -iname "*.jpg" -or -iname "*.jpeg" ) -type f -exec du {} ; $i
done






bash shell find






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 hours ago









Rui F Ribeiro

41.5k1483140




41.5k1483140










asked Jan 9 '13 at 16:15









batfastadbatfastad

7802920




7802920








  • 2





    Is $i the directory where you want to search for jp[e]g images, that is, the path? If so, "[the] path[s] must precede the expression" (the bit where you put the -inames). Why do you have a . after find instead of $i?

    – njsg
    Jan 9 '13 at 16:21













  • Question edited. Still getting the same error.

    – batfastad
    Jan 9 '13 at 17:28






  • 1





    Remove the $i at the end...

    – njsg
    Jan 9 '13 at 17:33














  • 2





    Is $i the directory where you want to search for jp[e]g images, that is, the path? If so, "[the] path[s] must precede the expression" (the bit where you put the -inames). Why do you have a . after find instead of $i?

    – njsg
    Jan 9 '13 at 16:21













  • Question edited. Still getting the same error.

    – batfastad
    Jan 9 '13 at 17:28






  • 1





    Remove the $i at the end...

    – njsg
    Jan 9 '13 at 17:33








2




2





Is $i the directory where you want to search for jp[e]g images, that is, the path? If so, "[the] path[s] must precede the expression" (the bit where you put the -inames). Why do you have a . after find instead of $i?

– njsg
Jan 9 '13 at 16:21







Is $i the directory where you want to search for jp[e]g images, that is, the path? If so, "[the] path[s] must precede the expression" (the bit where you put the -inames). Why do you have a . after find instead of $i?

– njsg
Jan 9 '13 at 16:21















Question edited. Still getting the same error.

– batfastad
Jan 9 '13 at 17:28





Question edited. Still getting the same error.

– batfastad
Jan 9 '13 at 17:28




1




1





Remove the $i at the end...

– njsg
Jan 9 '13 at 17:33





Remove the $i at the end...

– njsg
Jan 9 '13 at 17:33










2 Answers
2






active

oldest

votes


















2














for i in $(tree -dfi --noreport); do
find $i -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du {} ;
done


Drop the path name at the end of the find command and -type option should appear before any other options to make search a bit faster. This should do it.



By the way, to help you a bit, I would have done this in this way:



for i in $( tree -dfi --noreport ); do 
find $i -maxdepth 1 -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du '{}' ; | awk -v d=$i '{ j+=$1; } END{ printf("%s: %dn", d, j) }' | grep -Ev ": 0$"
done





share|improve this answer


























  • Thanks for that. Though it doesn't do what I was hoping. Also I think it borks on dir names containing spaces. A fault in my original approach.

    – batfastad
    Jan 10 '13 at 10:58



















2














Your immediate error is that extra $i at the end of the find invocation — just remove it. The order of arguments for find is first the directories to traverse, then the expression to match.



I don't get the point of the call to tree: find can do this. With GNU find (i.e. on Linux or Cygwin), assuming your directories don't contain insanely many .jpg files, the -execdir primary on find lets you run a command on all the matching files in a directory.



find . ( -name '*.jpg' -o -name '*.jpeg' ) -execdir sh -c 'echo "$(du -c "$@" | sed -n "$s/\t.*//p") ${PWD#$0/}"' $PWD {} +


Note that versions of GNU find prior to 4.5.9 have a bug that causes -execdir … {} + to run one command per file, which is no good here. So you may have to work harder.



You can traverse the directory tree in bash. Set the globstar option to enable the pattern **/, which matches any number of subdirectory levels, i.e. it enumerates subdirectories recursively. In each subdirectory, if there are JPEG files, call du to compute their total size.



shopt -s globstar
for d in **/*/; do
files=("$d/"*.jpg "$d/"*.jpeg)
total=$(du -s -- "$files" 2>/dev/null | tail -n 1)
total=${total%$'t'*}
echo "$total"$'t'"$d"
done





share|improve this answer
























  • Nice one... that one liner works beautifully. Nice tip on -execdir as well. Also seems to work with dir names containing spaces. I'm only just getting started with bash but I love how there are so many ways to do things like this. I couldn't find a way to do this under Windows so mounted the SMB share and ran this command. Nice!

    – batfastad
    Jan 10 '13 at 10:55













  • Also I did need -iname though as it was missing some directories containing .JPG/.JPEG files

    – batfastad
    Jan 10 '13 at 11:05











  • Actually I just noticed one thing, the same directory often appears twice with different sizes reported

    – batfastad
    Jan 10 '13 at 13:06











  • @benbradley The -execdir one-liner unfortunately only works on very recent (and IIRC a few older versions) of GNU find. I think most currently deployed systems have a buggy version where this reports every file independently. Try the bash loop (beware that I haven't tested it).

    – Gilles
    Jan 10 '13 at 13:14











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f60760%2fget-total-size-of-jpeg-images-per-directory-in-each-directory-containing-jpegs%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














for i in $(tree -dfi --noreport); do
find $i -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du {} ;
done


Drop the path name at the end of the find command and -type option should appear before any other options to make search a bit faster. This should do it.



By the way, to help you a bit, I would have done this in this way:



for i in $( tree -dfi --noreport ); do 
find $i -maxdepth 1 -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du '{}' ; | awk -v d=$i '{ j+=$1; } END{ printf("%s: %dn", d, j) }' | grep -Ev ": 0$"
done





share|improve this answer


























  • Thanks for that. Though it doesn't do what I was hoping. Also I think it borks on dir names containing spaces. A fault in my original approach.

    – batfastad
    Jan 10 '13 at 10:58
















2














for i in $(tree -dfi --noreport); do
find $i -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du {} ;
done


Drop the path name at the end of the find command and -type option should appear before any other options to make search a bit faster. This should do it.



By the way, to help you a bit, I would have done this in this way:



for i in $( tree -dfi --noreport ); do 
find $i -maxdepth 1 -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du '{}' ; | awk -v d=$i '{ j+=$1; } END{ printf("%s: %dn", d, j) }' | grep -Ev ": 0$"
done





share|improve this answer


























  • Thanks for that. Though it doesn't do what I was hoping. Also I think it borks on dir names containing spaces. A fault in my original approach.

    – batfastad
    Jan 10 '13 at 10:58














2












2








2







for i in $(tree -dfi --noreport); do
find $i -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du {} ;
done


Drop the path name at the end of the find command and -type option should appear before any other options to make search a bit faster. This should do it.



By the way, to help you a bit, I would have done this in this way:



for i in $( tree -dfi --noreport ); do 
find $i -maxdepth 1 -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du '{}' ; | awk -v d=$i '{ j+=$1; } END{ printf("%s: %dn", d, j) }' | grep -Ev ": 0$"
done





share|improve this answer















for i in $(tree -dfi --noreport); do
find $i -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du {} ;
done


Drop the path name at the end of the find command and -type option should appear before any other options to make search a bit faster. This should do it.



By the way, to help you a bit, I would have done this in this way:



for i in $( tree -dfi --noreport ); do 
find $i -maxdepth 1 -type f ( -iname "*.jpg" -or -iname "*.jpeg" ) -exec du '{}' ; | awk -v d=$i '{ j+=$1; } END{ printf("%s: %dn", d, j) }' | grep -Ev ": 0$"
done






share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 9 '13 at 23:38

























answered Jan 9 '13 at 23:20









Soumyadip DMSoumyadip DM

33928




33928













  • Thanks for that. Though it doesn't do what I was hoping. Also I think it borks on dir names containing spaces. A fault in my original approach.

    – batfastad
    Jan 10 '13 at 10:58



















  • Thanks for that. Though it doesn't do what I was hoping. Also I think it borks on dir names containing spaces. A fault in my original approach.

    – batfastad
    Jan 10 '13 at 10:58

















Thanks for that. Though it doesn't do what I was hoping. Also I think it borks on dir names containing spaces. A fault in my original approach.

– batfastad
Jan 10 '13 at 10:58





Thanks for that. Though it doesn't do what I was hoping. Also I think it borks on dir names containing spaces. A fault in my original approach.

– batfastad
Jan 10 '13 at 10:58













2














Your immediate error is that extra $i at the end of the find invocation — just remove it. The order of arguments for find is first the directories to traverse, then the expression to match.



I don't get the point of the call to tree: find can do this. With GNU find (i.e. on Linux or Cygwin), assuming your directories don't contain insanely many .jpg files, the -execdir primary on find lets you run a command on all the matching files in a directory.



find . ( -name '*.jpg' -o -name '*.jpeg' ) -execdir sh -c 'echo "$(du -c "$@" | sed -n "$s/\t.*//p") ${PWD#$0/}"' $PWD {} +


Note that versions of GNU find prior to 4.5.9 have a bug that causes -execdir … {} + to run one command per file, which is no good here. So you may have to work harder.



You can traverse the directory tree in bash. Set the globstar option to enable the pattern **/, which matches any number of subdirectory levels, i.e. it enumerates subdirectories recursively. In each subdirectory, if there are JPEG files, call du to compute their total size.



shopt -s globstar
for d in **/*/; do
files=("$d/"*.jpg "$d/"*.jpeg)
total=$(du -s -- "$files" 2>/dev/null | tail -n 1)
total=${total%$'t'*}
echo "$total"$'t'"$d"
done





share|improve this answer
























  • Nice one... that one liner works beautifully. Nice tip on -execdir as well. Also seems to work with dir names containing spaces. I'm only just getting started with bash but I love how there are so many ways to do things like this. I couldn't find a way to do this under Windows so mounted the SMB share and ran this command. Nice!

    – batfastad
    Jan 10 '13 at 10:55













  • Also I did need -iname though as it was missing some directories containing .JPG/.JPEG files

    – batfastad
    Jan 10 '13 at 11:05











  • Actually I just noticed one thing, the same directory often appears twice with different sizes reported

    – batfastad
    Jan 10 '13 at 13:06











  • @benbradley The -execdir one-liner unfortunately only works on very recent (and IIRC a few older versions) of GNU find. I think most currently deployed systems have a buggy version where this reports every file independently. Try the bash loop (beware that I haven't tested it).

    – Gilles
    Jan 10 '13 at 13:14
















2














Your immediate error is that extra $i at the end of the find invocation — just remove it. The order of arguments for find is first the directories to traverse, then the expression to match.



I don't get the point of the call to tree: find can do this. With GNU find (i.e. on Linux or Cygwin), assuming your directories don't contain insanely many .jpg files, the -execdir primary on find lets you run a command on all the matching files in a directory.



find . ( -name '*.jpg' -o -name '*.jpeg' ) -execdir sh -c 'echo "$(du -c "$@" | sed -n "$s/\t.*//p") ${PWD#$0/}"' $PWD {} +


Note that versions of GNU find prior to 4.5.9 have a bug that causes -execdir … {} + to run one command per file, which is no good here. So you may have to work harder.



You can traverse the directory tree in bash. Set the globstar option to enable the pattern **/, which matches any number of subdirectory levels, i.e. it enumerates subdirectories recursively. In each subdirectory, if there are JPEG files, call du to compute their total size.



shopt -s globstar
for d in **/*/; do
files=("$d/"*.jpg "$d/"*.jpeg)
total=$(du -s -- "$files" 2>/dev/null | tail -n 1)
total=${total%$'t'*}
echo "$total"$'t'"$d"
done





share|improve this answer
























  • Nice one... that one liner works beautifully. Nice tip on -execdir as well. Also seems to work with dir names containing spaces. I'm only just getting started with bash but I love how there are so many ways to do things like this. I couldn't find a way to do this under Windows so mounted the SMB share and ran this command. Nice!

    – batfastad
    Jan 10 '13 at 10:55













  • Also I did need -iname though as it was missing some directories containing .JPG/.JPEG files

    – batfastad
    Jan 10 '13 at 11:05











  • Actually I just noticed one thing, the same directory often appears twice with different sizes reported

    – batfastad
    Jan 10 '13 at 13:06











  • @benbradley The -execdir one-liner unfortunately only works on very recent (and IIRC a few older versions) of GNU find. I think most currently deployed systems have a buggy version where this reports every file independently. Try the bash loop (beware that I haven't tested it).

    – Gilles
    Jan 10 '13 at 13:14














2












2








2







Your immediate error is that extra $i at the end of the find invocation — just remove it. The order of arguments for find is first the directories to traverse, then the expression to match.



I don't get the point of the call to tree: find can do this. With GNU find (i.e. on Linux or Cygwin), assuming your directories don't contain insanely many .jpg files, the -execdir primary on find lets you run a command on all the matching files in a directory.



find . ( -name '*.jpg' -o -name '*.jpeg' ) -execdir sh -c 'echo "$(du -c "$@" | sed -n "$s/\t.*//p") ${PWD#$0/}"' $PWD {} +


Note that versions of GNU find prior to 4.5.9 have a bug that causes -execdir … {} + to run one command per file, which is no good here. So you may have to work harder.



You can traverse the directory tree in bash. Set the globstar option to enable the pattern **/, which matches any number of subdirectory levels, i.e. it enumerates subdirectories recursively. In each subdirectory, if there are JPEG files, call du to compute their total size.



shopt -s globstar
for d in **/*/; do
files=("$d/"*.jpg "$d/"*.jpeg)
total=$(du -s -- "$files" 2>/dev/null | tail -n 1)
total=${total%$'t'*}
echo "$total"$'t'"$d"
done





share|improve this answer













Your immediate error is that extra $i at the end of the find invocation — just remove it. The order of arguments for find is first the directories to traverse, then the expression to match.



I don't get the point of the call to tree: find can do this. With GNU find (i.e. on Linux or Cygwin), assuming your directories don't contain insanely many .jpg files, the -execdir primary on find lets you run a command on all the matching files in a directory.



find . ( -name '*.jpg' -o -name '*.jpeg' ) -execdir sh -c 'echo "$(du -c "$@" | sed -n "$s/\t.*//p") ${PWD#$0/}"' $PWD {} +


Note that versions of GNU find prior to 4.5.9 have a bug that causes -execdir … {} + to run one command per file, which is no good here. So you may have to work harder.



You can traverse the directory tree in bash. Set the globstar option to enable the pattern **/, which matches any number of subdirectory levels, i.e. it enumerates subdirectories recursively. In each subdirectory, if there are JPEG files, call du to compute their total size.



shopt -s globstar
for d in **/*/; do
files=("$d/"*.jpg "$d/"*.jpeg)
total=$(du -s -- "$files" 2>/dev/null | tail -n 1)
total=${total%$'t'*}
echo "$total"$'t'"$d"
done






share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 10 '13 at 0:27









GillesGilles

542k12810991616




542k12810991616













  • Nice one... that one liner works beautifully. Nice tip on -execdir as well. Also seems to work with dir names containing spaces. I'm only just getting started with bash but I love how there are so many ways to do things like this. I couldn't find a way to do this under Windows so mounted the SMB share and ran this command. Nice!

    – batfastad
    Jan 10 '13 at 10:55













  • Also I did need -iname though as it was missing some directories containing .JPG/.JPEG files

    – batfastad
    Jan 10 '13 at 11:05











  • Actually I just noticed one thing, the same directory often appears twice with different sizes reported

    – batfastad
    Jan 10 '13 at 13:06











  • @benbradley The -execdir one-liner unfortunately only works on very recent (and IIRC a few older versions) of GNU find. I think most currently deployed systems have a buggy version where this reports every file independently. Try the bash loop (beware that I haven't tested it).

    – Gilles
    Jan 10 '13 at 13:14



















  • Nice one... that one liner works beautifully. Nice tip on -execdir as well. Also seems to work with dir names containing spaces. I'm only just getting started with bash but I love how there are so many ways to do things like this. I couldn't find a way to do this under Windows so mounted the SMB share and ran this command. Nice!

    – batfastad
    Jan 10 '13 at 10:55













  • Also I did need -iname though as it was missing some directories containing .JPG/.JPEG files

    – batfastad
    Jan 10 '13 at 11:05











  • Actually I just noticed one thing, the same directory often appears twice with different sizes reported

    – batfastad
    Jan 10 '13 at 13:06











  • @benbradley The -execdir one-liner unfortunately only works on very recent (and IIRC a few older versions) of GNU find. I think most currently deployed systems have a buggy version where this reports every file independently. Try the bash loop (beware that I haven't tested it).

    – Gilles
    Jan 10 '13 at 13:14

















Nice one... that one liner works beautifully. Nice tip on -execdir as well. Also seems to work with dir names containing spaces. I'm only just getting started with bash but I love how there are so many ways to do things like this. I couldn't find a way to do this under Windows so mounted the SMB share and ran this command. Nice!

– batfastad
Jan 10 '13 at 10:55







Nice one... that one liner works beautifully. Nice tip on -execdir as well. Also seems to work with dir names containing spaces. I'm only just getting started with bash but I love how there are so many ways to do things like this. I couldn't find a way to do this under Windows so mounted the SMB share and ran this command. Nice!

– batfastad
Jan 10 '13 at 10:55















Also I did need -iname though as it was missing some directories containing .JPG/.JPEG files

– batfastad
Jan 10 '13 at 11:05





Also I did need -iname though as it was missing some directories containing .JPG/.JPEG files

– batfastad
Jan 10 '13 at 11:05













Actually I just noticed one thing, the same directory often appears twice with different sizes reported

– batfastad
Jan 10 '13 at 13:06





Actually I just noticed one thing, the same directory often appears twice with different sizes reported

– batfastad
Jan 10 '13 at 13:06













@benbradley The -execdir one-liner unfortunately only works on very recent (and IIRC a few older versions) of GNU find. I think most currently deployed systems have a buggy version where this reports every file independently. Try the bash loop (beware that I haven't tested it).

– Gilles
Jan 10 '13 at 13:14





@benbradley The -execdir one-liner unfortunately only works on very recent (and IIRC a few older versions) of GNU find. I think most currently deployed systems have a buggy version where this reports every file independently. Try the bash loop (beware that I haven't tested it).

– Gilles
Jan 10 '13 at 13:14


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f60760%2fget-total-size-of-jpeg-images-per-directory-in-each-directory-containing-jpegs%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

CARDNET

Boot-repair Failure: Unable to locate package grub-common:i386

濃尾地震